$ loading_
Control lab test instruments with natural language and manage multi-device sessions.
This MCP tool is described as controlling test instruments via SCPI, with no required secrets and no declared remote endpoints; the source is available for review, so overall risk appears relatively low. However, it can execute local code and control locally connected instruments, and sparse documentation plus low adoption warrant cautious deployment and environment scoping.
The materials state that no keys or environment variables are required. There is no indication that users must provide API tokens, account credentials, or third-party authentication, so credential exposure and misuse risk appears low.
No remote endpoint is declared, and there is no explicit description of cloud data exfiltration. However, 'auto-discovery' and multi-instrument sessions commonly imply discovering and connecting to instruments over local network or interfaces. No concrete red flag is present, but users should verify the actual discovery scope and whether it sends control commands to LAN devices.
The system flags executes-code, and the tool’s core function is sending SCPI control commands to instruments, which implies local execution and device-interaction capability. This is inherent to such a tool, and the materials do not show any clearly excessive privilege request beyond its stated purpose, so this is rated caution rather than high risk.
The description indicates multi-instrument session management and auto-discovery, implying access at least to locally visible instrument connection details and session state. The materials do not specify what local files are read or written, and there is no sign of overbroad authorization; however, because it can control lab equipment, users should assume it can affect connected device state and minimize its access scope.
Positive factors include being open source under the MIT License, making the code in principle auditable. However, the source is a third-party registry, the GitHub repo has 0 stars, maintenance status is unknown, and the README is absent, which limits verifiability and maturity. There is no high-risk red flag such as closed-source unexplained exfiltration, so this is rated caution.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Instrument MCP Server" yet — see the docs or source repo.
Connect to available instruments, identify the spectrum analyzer, set center frequency to 2.4 GHz, span to 100 MHz, reference level to 0 dBm, then run one scan and return the key configuration.
The tool auto-discovers and connects to the analyzer, sends the needed SCPI commands, and returns instrument status plus a parameter summary.
Find the connected programmable power supply, set channel 1 to 5 V with a 1 A current limit, enable output, and confirm the actual set values and output state.
The tool identifies the power supply and channel, applies voltage/current settings, toggles output, and returns execution results with confirmation.
Create a multi-instrument session that connects a spectrum analyzer and a power supply: power on the device under test first, then run a spectrum scan, and finally summarize the action log and current state of both instruments.
The tool creates a unified session, coordinates actions across multiple instruments in order, and outputs a full step log, status details, and result summary.
Control a bench oscilloscope over LAN for hardware debugging and validation.
Control Rigol oscilloscopes with AI through automated SCPI command execution.
Control bench power supplies for precise power cycling, telemetry, and bootloader probing.
Control quantum lab instruments and measurement systems via QCodes and JupyterLab.
Manage router settings and network control through natural language commands.
Test all MCP protocol features when building and validating clients.