Rigol Oscilloscope
PYPI · LABMCP-RIGOL-SCOPE
MCP server for Rigol oscilloscopes (DS1000Z, MSO5000, DHO series): measurements and waveforms.
Available components
Last scanned (18 hours ago)
Scores higher than 78% of PyPI servers
Category IoT and Hardware
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. How we score → Why this is hard to score →
Supply Chain Security49
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to K-Dense-AI/lab-instrument-mcps). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 55 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1556 tokens (~97/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
- Structured output schemas are declared (94% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 13 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 11 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 −2
- Stability: pass → 0.87 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/labmcp-rigol-scope@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | K-Dense-AI/lab-instrument-mcps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/K-Dense-AI/lab-instrument-mcps/.github/workflows/release.yml@refs/tags/labmcp-rigol-scope-v0.1.2 |
| Rekor log index | 2969517940 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:fbcb5dc38796d290d59ceaeb51d5dbfe9dba5053ca4fb46e2809c0421c731a3f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
autoscale Autoscale ~61
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| timestamp | string | yes | – |
| trigger_status | string | yes | – |
No examples provided.
capture_waveform Capture Waveform ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| clipped_fraction | number | yes | Fraction of points at the ADC limits (byte code 0 or 255): the trace is clipped, amplitudes are wrong |
| downsample_factor | integer | yes | Points per min/max pair (1 = every point returned) |
| mode | string | yes | – |
| points | integer | yes | – |
| sample_interval_s | number | yes | – |
| saved_to | – | yes | – |
| start_time_s | number | yes | Time of the first point relative to the trigger |
| stats | object | yes | – |
| time_s | array | yes | – |
| timestamp | string | yes | – |
| volts | array | yes | Downsampled trace: each block of downsample_factor points keeps its minimum and maximum sample (with their exact times), so glitches are not lost |
No examples provided.
force_trigger Force Trigger ~32
Force one trigger (FORCE key). Only has an effect in NORMal or SINGle sweep while waiting.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| timestamp | string | yes | – |
| trigger_status | string | yes | – |
No examples provided.
get_command_log Get Command Log ~46
Return the most recent raw commands sent to / replies received from the instrument (newest last). Useful for debugging and for recording what was done.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_connection_info Get Connection Info ~40
Report which instrument is connected (identity, address, simulated or real), whether the server is read-only, and the active safety limits. Call this first.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_device_info Get Device Info ~44
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| analog_channels | integer | yes | – |
| family | string | yes | Command profile: DS1000Z, MSO5000 or DHO |
| firmware | string | yes | – |
| horizontal_divisions | integer | yes | – |
| manufacturer | string | yes | – |
| memory_depth | – | yes | – |
| model | string | yes | – |
| programming_guide | string | yes | – |
| sample_rate_sa_s | number | yes | – |
| screen_points | integer | yes | Points per channel in a screen capture |
| serial | string | yes | – |
| timestamp | string | yes | – |
No examples provided.
get_settings Get Settings ~63
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | – |
| memory_depth | – | yes | – |
| sample_rate_sa_s | number | yes | – |
| timebase | object | yes | – |
| timestamp | string | yes | – |
| trigger | object | yes | – |
No examples provided.
measure Measure ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| items | array | – | Parameters to measure |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| measurements | array | yes | – |
| timestamp | string | yes | – |
No examples provided.
reconnect Reconnect ~35
Close and re-open the connection to the instrument (e.g. after it was power cycled or a cable was re-plugged).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
run Run ~13
Start continuous acquisition (RUN).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| timestamp | string | yes | – |
| trigger_status | string | yes | – |
No examples provided.
screenshot Screenshot ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
set_channel Set Channel ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bandwidth_limit_20mhz | – | – | 20 MHz bandwidth limit on/off |
| channel | integer | yes | 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| bandwidth_limit | string | yes | – |
| channel | integer | yes | – |
| coupling | string | yes | – |
| enabled | boolean | yes | – |
| offset_v | number | yes | – |
| probe_ratio | number | yes | – |
| scale_v_per_div | number | yes | – |
No examples provided.
set_timebase Set Timebase ~57
Set the main timebase scale and/or offset. Returns the applied values.
| Name | Type | Req | Description |
|---|---|---|---|
| offset_s | – | – | Horizontal (trigger) offset in s |
| scale_s_per_div | – | – | Horizontal scale in s/div (1-2-5 steps) |
| Name | Type | Req | Description |
|---|---|---|---|
| offset_s | number | yes | – |
| scale_s_per_div | number | yes | – |
| window_s | number | yes | Time shown across the screen (scale x divisions) |
No examples provided.
set_trigger Set Trigger ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| level_v | – | – | – |
| slope | – | – | – |
| source | – | – | – |
| status | string | yes | TD (triggered), WAIT, RUN, AUTO or STOP |
| sweep | string | yes | AUTO, NORM or SING |
| type | string | yes | – |
No examples provided.
single Single ~86
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| wait_s | number | – | Seconds to wait for the trigger; 0 = just arm |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| timestamp | string | yes | – |
| trigger_status | string | yes | – |
No examples provided.
stop Stop ~27
Stop acquisition (STOP) and freeze the current waveforms, e.g. before reading deep memory.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| timestamp | string | yes | – |
| trigger_status | string | yes | – |
No examples provided.
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.
pypi · labmcp-rigol-scope
claude mcp add k-dense-ai-labmcp-rigol-scope -- uvx labmcp-rigol-scope
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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 21 November 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.
What did VerifyMCP test on the Rigol Oscilloscope MCP server?
VerifyMCP ran 15 checks on Rigol Oscilloscope, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Rigol Oscilloscope: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.