# Rigol Oscilloscope (pypi · labmcp-rigol-scope)

MCP server for Rigol oscilloscopes (DS1000Z, MSO5000, DHO series): measurements and waveforms.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- pypi · `labmcp-rigol-scope`: 66/100 (this document), [markdown](https://verifymcp.io/servers/k-dense-ai-labmcp-rigol-scope/labmcp-rigol-scope.md), [page](https://verifymcp.io/servers/k-dense-ai-labmcp-rigol-scope/labmcp-rigol-scope)

## Channel facts

- Registry: `pypi`
- Package: `labmcp-rigol-scope`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-30.

- **Supply Chain Security**: 49/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 2 of 18 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to K-Dense-AI/lab-instrument-mcps).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1556 tokens (~97/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
  - Structured output schemas are declared (94% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Rigol Oscilloscope MCP server?

Rigol Oscilloscope runs locally as a PyPI package, launched with uvx labmcp-rigol-scope. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add k-dense-ai-labmcp-rigol-scope -- uvx labmcp-rigol-scope
```

### Cursor

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-rigol-scope": {
      "command": "uvx",
      "args": [
        "labmcp-rigol-scope"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k-dense-ai-labmcp-rigol-scope": {
      "command": "uvx",
      "args": [
        "labmcp-rigol-scope"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add k-dense-ai-labmcp-rigol-scope -- uvx labmcp-rigol-scope
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-dense-ai-labmcp-rigol-scope": {
      "type": "local",
      "command": [
        "uvx",
        "labmcp-rigol-scope"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k-dense-ai-labmcp-rigol-scope --command uvx --arg labmcp-rigol-scope
```

### Hermes

```yaml
mcp_servers:
  k-dense-ai-labmcp-rigol-scope:
    command: "uvx"
    args: ["labmcp-rigol-scope"]
```

### Netclaw

```json
{
  "McpServers": {
    "k-dense-ai-labmcp-rigol-scope": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "labmcp-rigol-scope"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add k-dense-ai-labmcp-rigol-scope -t stdio -c uvx -a labmcp-rigol-scope
```

### Other

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-rigol-scope": {
      "command": "uvx",
      "args": [
        "labmcp-rigol-scope"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 66, −5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 71, 0)

- [functional] Package version: 0.1.1 → 0.1.2

### 2026-09-26 (score 71)

First indexed and scored.

## MCP tools (16)

### `get_connection_info` (~40 tokens)

Get Connection Info

Report which instrument is connected (identity, address, simulated or real),
whether the server is read-only, and the active safety limits. Call this first.

### `get_command_log` (~46 tokens)

Get Command Log

Return the most recent raw commands sent to / replies received from the
instrument (newest last). Useful for debugging and for recording what was done.

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (array)

### `reconnect` (~35 tokens)

Reconnect

Close and re-open the connection to the instrument (e.g. after it was power
cycled or a cable was re-plugged).

### `get_device_info` (~44 tokens)

Get Device Info

Identify the oscilloscope (model, serial, firmware), the command family used for it, the
number of analog channels, and the current sample rate and memory depth.

Output parameters:

- `analog_channels` (integer)
- `family` (string): Command profile: DS1000Z, MSO5000 or DHO
- `firmware` (string)
- `horizontal_divisions` (integer)
- `manufacturer` (string)
- `memory_depth`
- `model` (string)
- `programming_guide` (string)
- `sample_rate_sa_s` (number)
- `screen_points` (integer): Points per channel in a screen capture
- `serial` (string)
- `timestamp` (string)

### `get_settings` (~63 tokens)

Get Settings

Read the current vertical settings of every channel (on/off, V/div, offset, coupling, probe
ratio, bandwidth limit), the timebase, the trigger (type, sweep, status, edge source/level/slope)
and the acquisition sample rate / memory depth.

Output parameters:

- `channels` (array)
- `memory_depth`
- `sample_rate_sa_s` (number)
- `timebase` (object)
- `timestamp` (string)
- `trigger` (object)

### `autoscale` (~61 tokens)

Autoscale

Run the scope's automatic setup (AUTO key): it picks vertical scales, timebase and trigger
for the connected signals. This overwrites the user's current setup - only use it when asked.
Needs signals of roughly >20 mVpp and >40 Hz.

Output parameters:

- `message` (string)
- `timestamp` (string)
- `trigger_status` (string)

### `run` (~13 tokens)

Run

Start continuous acquisition (RUN).

Output parameters:

- `message` (string)
- `timestamp` (string)
- `trigger_status` (string)

### `stop` (~27 tokens)

Stop

Stop acquisition (STOP) and freeze the current waveforms, e.g. before reading deep memory.

Output parameters:

- `message` (string)
- `timestamp` (string)
- `trigger_status` (string)

### `single` (~86 tokens)

Single

Arm a single acquisition (SINGLE key): the scope triggers once, then stops. With wait_s > 0
it waits until the acquisition is complete (status STOP). If the trigger condition is never met
the status stays WAIT - check the trigger level/source or use `force_trigger`.

Input parameters:

- `wait_s` (number): Seconds to wait for the trigger; 0 = just arm

Output parameters:

- `message` (string)
- `timestamp` (string)
- `trigger_status` (string)

### `force_trigger` (~32 tokens)

Force Trigger

Force one trigger (FORCE key). Only has an effect in NORMal or SINGle sweep while waiting.

Output parameters:

- `message` (string)
- `timestamp` (string)
- `trigger_status` (string)

### `set_channel` (~166 tokens)

Set Channel

Change a channel's vertical settings; unspecified settings are left alone. The probe ratio
is applied first because it changes the valid scale range. Returns the settings the scope
actually applied (the scale snaps to 1-2-5 steps). Rejected values are reported from the
scope's error queue.

Input parameters:

- `bandwidth_limit_20mhz`: 20 MHz bandwidth limit on/off
- `channel` (integer, required): Analog channel number
- `coupling`
- `enabled`: Show (acquire) the channel
- `offset_v`: Vertical offset in V
- `probe_ratio`: Probe attenuation, e.g. 1 or 10 - must match the probe
- `scale_v_per_div`: Vertical scale in V/div (1-2-5 steps)

Output parameters:

- `bandwidth_limit` (string)
- `channel` (integer)
- `coupling` (string)
- `enabled` (boolean)
- `offset_v` (number)
- `probe_ratio` (number)
- `scale_v_per_div` (number)

### `set_timebase` (~57 tokens)

Set Timebase

Set the main timebase scale and/or offset. Returns the applied values.

Input parameters:

- `offset_s`: Horizontal (trigger) offset in s
- `scale_s_per_div`: Horizontal scale in s/div (1-2-5 steps)

Output parameters:

- `offset_s` (number)
- `scale_s_per_div` (number)
- `window_s` (number): Time shown across the screen (scale x divisions)

### `set_trigger` (~96 tokens)

Set Trigger

Configure an edge trigger (source, level, slope) and the sweep mode. Sets the trigger type to
EDGE. The level must lie within the source channel's screen range.

Input parameters:

- `level_v`: Trigger level in V (displayed units)
- `slope`
- `source_channel`: Analog channel to trigger on
- `sweep`: auto = free-run when not triggered; normal = only on trigger; single = once

Output parameters:

- `level_v`
- `slope`
- `source`
- `status` (string): TD (triggered), WAIT, RUN, AUTO or STOP
- `sweep` (string): AUTO, NORM or SING
- `type` (string)

### `measure` (~93 tokens)

Measure

Read the scope's automatic measurements for one channel: voltages (Vpp, Vmax, Vmin, Vtop,
Vbase, Vamp, Vavg, Vrms, overshoot, preshoot) and timing (period, frequency, rise/fall time,
\+/- width, +/- duty). Values the scope cannot determine are null.

Input parameters:

- `channel` (integer, required)
- `items` (array): Parameters to measure

Output parameters:

- `channel` (integer)
- `measurements` (array)
- `timestamp` (string)

### `capture_waveform` (~164 tokens)

Capture Waveform

Capture a channel's waveform, scaled to volts and seconds with the scope's waveform preamble,
and return statistics plus a downsampled trace; optionally save all points to CSV.

'memory' mode reads the whole record (bounded by the `max_memory_points` limit) in batches and
requires the scope to be stopped; 'screen' works while running.

Input parameters:

- `channel` (integer, required)
- `max_points` (integer): Max points returned (the data is downsampled)
- `mode` (string): 'screen' = the displayed points (1000-1200); 'memory' = full acquisition memory (scope must be stopped)
- `save_path`: Write every point (time_s, volts) to this new .csv file (never overwritten)

Output parameters:

- `channel` (integer)
- `clipped_fraction` (number): Fraction of points at the ADC limits (byte code 0 or 255): the trace is clipped, amplitudes are wrong
- `downsample_factor` (integer): Points per min/max pair (1 = every point returned)
- `mode` (string)
- `points` (integer)
- `sample_interval_s` (number)
- `saved_to`
- `start_time_s` (number): Time of the first point relative to the trigger
- `stats` (object)
- `time_s` (array)
- `timestamp` (string)
- `volts` (array): Downsampled trace: each block of downsample_factor points keeps its minimum and maximum sample (with their exact times), so glitches are not lost

### `screenshot` (~104 tokens)

Screenshot

Save a screenshot of the oscilloscope display (PNG; BMP on the MSO5000) and return its path.
For PNG screenshots the image is also returned so the model can look at the screen.

Input parameters:

- `include_image` (boolean): Also return the image to the client (PNG only)
- `save_path`: New image file to write (.png; .bmp on the MSO5000; never overwritten); default: a timestamped file in the system temp folder

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/k-dense-ai-labmcp-rigol-scope/labmcp-rigol-scope#diagnostics

## Score history

- 2026-09-30: 66
- 2026-09-29: 66
- 2026-09-28: 66
- 2026-09-27: 71
- 2026-09-26: 71

## Common questions

### What is the Rigol Oscilloscope MCP server?

Rigol Oscilloscope is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-rigol-scope. MCP server for Rigol oscilloscopes (DS1000Z, MSO5000, DHO series): measurements and waveforms. This page covers its PyPI package (labmcp-rigol-scope).

### Is the Rigol Oscilloscope MCP server safe to use?

Rigol Oscilloscope scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 September 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Rigol Oscilloscope MCP server expose?

Rigol Oscilloscope exposes 16 tools: get_connection_info, get_command_log, reconnect, get_device_info, get_settings, and 11 more. Their descriptions and schemas cost roughly 1,127 tokens of context every time the server is loaded.

### Is the Rigol Oscilloscope MCP server still maintained?

Rigol Oscilloscope is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Rigol Oscilloscope MCP server under?

Rigol Oscilloscope declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/labmcp-rigol-scope/
- Socket report: https://socket.dev/pypi/package/labmcp-rigol-scope
- Repository: https://github.com/K-Dense-AI/lab-instrument-mcps
- Website: https://github.com/K-Dense-AI/lab-instrument-mcps/tree/main/servers/engineering/rigol-oscilloscope
- Changelog RSS feed: https://verifymcp.io/servers/k-dense-ai-labmcp-rigol-scope/labmcp-rigol-scope.xml
- Changelog JSON feed: https://verifymcp.io/servers/k-dense-ai-labmcp-rigol-scope/labmcp-rigol-scope.json
- HTML version of this page: https://verifymcp.io/servers/k-dense-ai-labmcp-rigol-scope/labmcp-rigol-scope