sigrok MCP Server
OCI · GHCR.IO/KENOSINC/SIGROK-MCP-SERVER:0.2.0
Wraps sigrok-cli for signal analysis: capture data, decode protocols, and query instruments.
Available components
Last scanned (21 hours ago)
Scores higher than 95% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 252 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1165 tokens (~83/item across 14 items; 13 tools + 1 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 −3
- Stability: pass → 0.77 functional
- 12 Oct 26 0
- Stability: 0.93 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed oci/ghcr.io/kenosinc/sigrok-mcp-server:0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
capture_data ~198
Capture communication data from a connected device and save to file. Either 'samples' or 'time' must be specified.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | string | – | Channels to use (e.g. 'D0,D1,D2') |
| config | string | – | Device configuration (e.g. 'samplerate=1M') |
| conn | string | – | Connection string for serial/network devices (e.g. '/dev/ttyUSB0:serialcomm=115200/8n1') |
| driver | string | yes | Hardware driver ID (e.g. 'fx2lafw', 'demo') |
| output_file | string | – | Output filename (auto-generated if omitted) |
| samples | number | – | Number of samples to acquire |
| time | number | – | How long to sample in milliseconds |
| triggers | string | – | Trigger configuration (e.g. 'D0=r') |
| wait_trigger | boolean | – | Wait for trigger before capturing |
No output schema declared.
No examples provided.
check_firmware_status ~44
Check firmware file availability in standard sigrok firmware directories. Returns which directories exist and what firmware files are present. Use this to diagnose device detection issues caused by missing firmware.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
decode_protocol ~146
Decode protocol data from a captured file using sigrok protocol decoders.
| Name | Type | Req | Description |
|---|---|---|---|
| annotations | string | – | Decoder annotation filter (e.g. 'uart=rx-data') |
| input_file | string | yes | Input filename |
| input_format | string | – | Input format (e.g. 'vcd', 'binary') |
| json_trace | boolean | – | Output in Google Trace Event JSON format |
| meta_output | string | – | Decoder meta output filter (e.g. 'uart=baud') |
| protocol_decoders | string | yes | Protocol decoders to apply (e.g. 'uart:baudrate=9600') |
| show_sample_numbers | boolean | – | Include sample numbers in output |
No output schema declared.
No examples provided.
get_device_profile ~88
Look up a device profile by name, model, manufacturer, or *IDN? response string. Returns connection settings (baudrate, parity, etc.), supported commands with examples, and device-specific notes. Use this before serial_query to get the correct settings for a device.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Device name, model, manufacturer, or *IDN? response string to match against |
No output schema declared.
No examples provided.
list_input_formats ~27
List all supported input file formats. Returns an array of {id, description} objects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_output_formats ~27
List all supported output file formats. Returns an array of {id, description} objects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_supported_decoders ~28
List all supported protocol decoders. Returns an array of {id, description} objects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_supported_hardware ~27
List all supported hardware drivers. Returns an array of {id, description} objects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_devices ~225
Scan for connected hardware devices. Returns {devices, warnings, hint} where devices is an array of {driver, description} objects. Warnings indicate firmware-related issues for devices that could not be initialized. When driver and conn are provided, performs a targeted scan for a specific serial/network device (e.g. SCPI instruments). SCPI driver categories: 'scpi-dmm' (multimeters), 'scpi-pps' (power supplies), or vendor-specific drivers like 'rigol-ds' (oscilloscopes). Example: driver='scpi-dmm', conn='/dev/ttyUSB0:serialcomm=115200/8n1'.
| Name | Type | Req | Description |
|---|---|---|---|
| conn | string | – | Connection string for targeted scanning (e.g. '/dev/ttyUSB0:serialcomm=115200/8n1', 'tcp-raw/192.168.1.100/5555') |
| driver | string | – | Hardware driver ID for targeted scanning (e.g. 'scpi-dmm', 'scpi-pps', 'rigol-ds') |
No output schema declared.
No examples provided.
serial_query ~200
Send a command string over a serial port and return the device response. Works with any serial-attached instrument that accepts text commands (e.g. SCPI). Independent of sigrok-cli.
| Name | Type | Req | Description |
|---|---|---|---|
| baudrate | number | – | Baud rate (default 9600) |
| command | string | yes | Command to send (e.g. '*IDN?', 'MEAS:VOLT:DC?') |
| databits | number | – | Data bits: 5, 6, 7, or 8 (default 8) |
| parity | string | – | Parity: none, odd, even, mark, space (default 'none') |
| port | string | yes | Serial device path (e.g. '/dev/ttyUSB0') |
| stopbits | string | – | Stop bits: 1, 1.5, 2 (default '1') |
| timeout_ms | number | – | Read timeout in milliseconds (default 1000) |
No output schema declared.
No examples provided.
show_decoder_details ~53
Show detailed information about a specific protocol decoder, including options, channels, annotation classes, and documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| decoder | string | yes | Protocol decoder ID (e.g. 'uart', 'spi', 'i2c') |
No output schema declared.
No examples provided.
show_driver_details ~57
Show detailed information about a specific hardware driver, including supported functions, scan options, and connected devices.
| Name | Type | Req | Description |
|---|---|---|---|
| driver | string | yes | Hardware driver ID (e.g. 'demo', 'fx2lafw', 'rigol-ds') |
No output schema declared.
No examples provided.
show_version ~19
Show sigrok-cli version information, including library versions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the sigrok MCP Server server?
sigrok MCP Server runs locally as a container image, launched with docker run --rm -i -e SIGROK_CLI_PATH -e SIGROK_TIMEOUT_SECONDS -e SIGROK_WORKING_DIR ghcr.io/kenosinc/sigrok-mcp-server:0.2.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/kenosinc/sigrok-mcp-server:0.2.0
claude mcp add kenosinc-sigrok-mcp-server -- docker run --rm -i -e SIGROK_CLI_PATH -e SIGROK_TIMEOUT_SECONDS -e SIGROK_WORKING_DIR ghcr.io/kenosinc/sigrok-mcp-server:0.2.0
This image reads SIGROK_CLI_PATH, SIGROK_TIMEOUT_SECONDS and SIGROK_WORKING_DIR. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the sigrok MCP Server server?
sigrok MCP Server is listed in the public MCP registry as io.github.KenosInc/sigrok-mcp-server. Wraps sigrok-cli for signal analysis: capture data, decode protocols, and query instruments. This page covers its container image (ghcr.io/kenosinc/sigrok-mcp-server:0.2.0).
Is the sigrok MCP Server server safe to use?
sigrok MCP Server scores 56 out of 100 on VerifyMCP. 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 sigrok MCP Server server expose?
sigrok MCP Server exposes 13 tools: capture_data, check_firmware_status, decode_protocol, get_device_profile, list_input_formats, and 8 more. Their descriptions and schemas cost roughly 1,139 tokens of context every time the server is loaded.
Is the sigrok MCP Server server still maintained?
sigrok MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 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 sigrok MCP Server server under?
sigrok MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.