RigolSAFE
Rigol Scope MCP for use in Claude Code, Cursor, Codex etc. for agentic electrical engineering
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
MCP server for controlling Rigol DS1000Z and DHO series oscilloscopes over LAN or USB. Exposes the scope as a set of tools that Claude (or any MCP client) can call to take measurements, configure the instrument, and capture screenshots — entirely through natural language.
Example: unknown signal characterisation in Claude
Unknown signal (square wave into LCR trap), wrong channel enabled, invalid timebase/voltage/trigger. Claude identifies the signal type, corrects the setup, and characterises the waveform.
Supported Hardware
Rigol DS1000Z / MSO1000Z series (8-bit):
Rigol DHO series (12-bit):
Other DHO models (DHO900/1000/4000 families) likely work with the same SCPI dialect but are not verified.
The scope connects either over your local network via Ethernet (rear panel RJ45) or over USB (rear panel USB-B device port). LAN is the default; USB is used when RIGOL_USB is set (see Configuration). USB transport has been validated on DS1000Z; DHO support has so far been validated over LAN only.
Requirements
- Python 3.11+
- uv
- A Rigol DS1000Z (LAN or USB) or DHO series scope (LAN) connected to your computer
- For LAN: SCPI over TCP/IP enabled on the scope (on by default)
- For USB: a VISA driver on the scope's USB interface — either the native USBTMC driver
(e.g. from Rigol UltraSigma / any NI-VISA runtime) or WinUSB via Zadig (see [USB connection](#usb-conne
8ca2fbeba440OBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add rigol-mcp -- uvx rigol-mcp
{
"mcpServers": {
"rigol-mcp": {
"command": "uvx",
"args": [
"rigol-mcp"
]
}
}
}Exposed tools (5)
4 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
check_error | read | Query the SCPI error queue. Returns the error if present, or |
disconnect | read | Release this server |
export_acquisition | read | Export the complete stopped acquisition memory to uint8 binary files and a |
get_acquisition_info | read | Read acquisition status, sample rate, memory-depth setting, enabled channels, |
run | write | Start continuous acquisition. Returns trigger status after the command. Do not call concurrently with any other rigol tool. |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (2)
"inv_delta_x is 1/Δt — the frequency between the two cursors. "
Verify in browser: `http://192.168.1.123/DS1000Z_WelcomePage.html`
Gates applied: no_behavioural_pass.
8ca2fbeba440full audit observations/trust-audit/mcp-server/erebusnz__rigol.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 8ca2fbeba440 | SAFE | B | 89 | first audit |
Questions
What is the Rigol MCP server?
Rigol Scope MCP for use in Claude Code, Cursor, Codex etc. for agentic electrical engineering
What tools does Rigol expose?
5 in total: 4 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Rigol safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Rigol need?
No credential environment variables were found in its source, so it appears to need none.
How does Rigol run?
It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as rigol-mcp.
How current is this page?
The grade is for one exact copy of the source (8ca2fbeba440), read on 2026-10-10. The repository is watched and re-audited when it changes.