# Siglent SDM3045X multimeter (pypi · mcp-server-siglent-sdm3045x) Measurements with a Siglent SDM3045X bench multimeter via USB or LAN (unofficial) - Trust score: 79/100 (medium) - Change this week: +19 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - pypi · `mcp-server-siglent-sdm3045x`: 79/100 (this document), [markdown](https://verifymcp.io/servers/shaag7967-mcp-server-siglent-sdm3045x/mcp-server-siglent-sdm3045x.md), [page](https://verifymcp.io/servers/shaag7967-mcp-server-siglent-sdm3045x/mcp-server-siglent-sdm3045x) ## Channel facts - Registry: `pypi` - Package: `mcp-server-siglent-sdm3045x` - Version: `0.1.1` - 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-11-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - Runs uv_build at install time, a recognised build step with no custom scripting around it. - 1 of 32 dependencies flagged as unhealthy. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to shaag7967/mcp-server-siglent-sdm3045x). - Clear OSI-approved license (MIT). - Actively maintained (last published 6 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 54/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 1690 tokens (~338/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 71/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - Structured output schemas are declared (100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 6 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). ## Install ### How do I install the Siglent SDM3045X multimeter MCP server? Siglent SDM3045X multimeter runs locally as a PyPI package, launched with uvx mcp-server-siglent-sdm3045x. 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 shaag7967-mcp-server-siglent-sdm3045x -- uvx mcp-server-siglent-sdm3045x ``` ### Cursor ```json { "mcpServers": { "shaag7967-mcp-server-siglent-sdm3045x": { "command": "uvx", "args": [ "mcp-server-siglent-sdm3045x" ] } } } ``` ### VS Code ```json { "servers": { "shaag7967-mcp-server-siglent-sdm3045x": { "command": "uvx", "args": [ "mcp-server-siglent-sdm3045x" ] } } } ``` ### Codex ```bash codex mcp add shaag7967-mcp-server-siglent-sdm3045x -- uvx mcp-server-siglent-sdm3045x ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "shaag7967-mcp-server-siglent-sdm3045x": { "type": "local", "command": [ "uvx", "mcp-server-siglent-sdm3045x" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add shaag7967-mcp-server-siglent-sdm3045x --command uvx --arg mcp-server-siglent-sdm3045x ``` ### Hermes ```yaml mcp_servers: shaag7967-mcp-server-siglent-sdm3045x: command: "uvx" args: ["mcp-server-siglent-sdm3045x"] ``` ### Netclaw ```json { "McpServers": { "shaag7967-mcp-server-siglent-sdm3045x": { "Transport": "stdio", "Command": "uvx", "Arguments": [ "mcp-server-siglent-sdm3045x" ] } } } ``` ### Vellum ```bash assistant mcp add shaag7967-mcp-server-siglent-sdm3045x -t stdio -c uvx -a mcp-server-siglent-sdm3045x ``` ### Other ```json { "mcpServers": { "shaag7967-mcp-server-siglent-sdm3045x": { "command": "uvx", "args": [ "mcp-server-siglent-sdm3045x" ] } } } ``` ## 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-11-05 (score 79, +16) - [security improvement] Malware scan: unverified → pass ### 2026-11-03 (score 63, −14) - [security regression] Malware scan: pass → unverified ### 2026-11-01 (score 77, +1) No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-31 (score 76, +15) - [security improvement] Malware scan: unverified → pass ### 2026-10-30 (score 61, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-29 (score 60, −15) - [security regression] Malware scan: pass → unverified - [functional] Package version: 0.1.0 → 0.1.1 ### 2026-10-28 (score 75) First indexed and scored. ## MCP tools (5) ### `read` (~71 tokens) Take one reading with the function, range and speed currently set on the instrument. Function, range and speed are kept; the trigger is set to immediate with one reading per trigger, as measure does. Returns value, unit, range, timestamp (UTC) and, where the data sheet allows, the accuracy. ### `measure` (~420 tokens) Select a measurement function and take one reading. This switches the instrument (front panel included) to the given function, with autorange unless a range is given. Returns value, unit, range used, timestamp (UTC) and, where the data sheet allows, the accuracy of the reading. Args: function: Measurement function. Leads in HI/LO for voltage, resistance_2w, capacitance, frequency, period, continuity, diode and temperature; in I/LO for currents; resistance_4w also uses HI Sense/LO Sense. range: Fixed range in V, A, Ω or F; omit for autorange. dc_voltage 0.6, 6, 60, 600, 1000; ac_voltage 0.6, 6, 60, 600, 750; dc_current 0.0006, 0.006, 0.06, 0.6, 6, 10; ac_current 0.06, 0.6, 6, 10; resistance_2w/resistance_4w 600, 6000, 60000, 600000, 6e6, 6e7, 1e8; capacitance 2e-9, 2e-8, 2e-7, 2e-6, 2e-5, 0.0002, 0.01. Other functions have no range. speed: Only for dc_voltage, dc_current, resistance_2w, resistance_4w: slow (10 PLC, default, most accurate), medium (1 PLC), fast (0.3 PLC). sensor: Required for temperature: pt100 (RTD) or thermocouple type B, E, J, K, N, R, S or T. Input parameters: - `function` (string, required) - `range` - `sensor` - `speed` ### `sample` (~507 tokens) Record timestamped readings at a fixed interval and return statistics plus all samples. Readings are paced by this computer. A reading takes about 0.3 s at speed slow and in most other functions, 0.6 s for frequency and period; with a shorter interval readings are taken back to back, and none starts later than one interval after duration_s, so the recording ends on time with fewer samples. Without function the present function and range are kept; otherwise they are set as in measure. Args: duration_s: Recording time in seconds (max 600). interval_s: Time between readings in seconds (min 0.1). function: Measurement function. Leads in HI/LO for voltage, resistance_2w, capacitance, frequency, period, continuity, diode and temperature; in I/LO for currents; resistance_4w also uses HI Sense/LO Sense. range: Fixed range in V, A, Ω or F; omit for autorange. dc_voltage 0.6, 6, 60, 600, 1000; ac_voltage 0.6, 6, 60, 600, 750; dc_current 0.0006, 0.006, 0.06, 0.6, 6, 10; ac_current 0.06, 0.6, 6, 10; resistance_2w/resistance_4w 600, 6000, 60000, 600000, 6e6, 6e7, 1e8; capacitance 2e-9, 2e-8, 2e-7, 2e-6, 2e-5, 0.0002, 0.01. Other functions have no range. speed: Only for dc_voltage, dc_current, resistance_2w, resistance_4w: slow (10 PLC, default, most accurate), medium (1 PLC), fast (0.3 PLC). sensor: Required for temperature: pt100 (RTD) or thermocouple type B, E, J, K, N, R, S or T. Input parameters: - `duration_s` (number) - `function` - `interval_s` (number) - `range` - `sensor` - `speed` ### `burst` (~492 tokens) Take a series of readings as fast as the instrument can and return statistics plus all values. Readings are paced by the instrument and have no individual timestamps. Approximate rates (50 Hz mains): dc_voltage, dc_current and resistance 4/s at speed slow, 40/s medium, 175/s fast; ac functions and temperature 4/s; frequency and period 2/s. Bursts estimated to take longer than 600 s are refused. Without function the present function and range are kept; otherwise they are set as in measure. Args: count: Number of readings, 1 to 10000. function: Measurement function. Leads in HI/LO for voltage, resistance_2w, capacitance, frequency, period, continuity, diode and temperature; in I/LO for currents; resistance_4w also uses HI Sense/LO Sense. range: Fixed range in V, A, Ω or F; omit for autorange. dc_voltage 0.6, 6, 60, 600, 1000; ac_voltage 0.6, 6, 60, 600, 750; dc_current 0.0006, 0.006, 0.06, 0.6, 6, 10; ac_current 0.06, 0.6, 6, 10; resistance_2w/resistance_4w 600, 6000, 60000, 600000, 6e6, 6e7, 1e8; capacitance 2e-9, 2e-8, 2e-7, 2e-6, 2e-5, 0.0002, 0.01. Other functions have no range. speed: Only for dc_voltage, dc_current, resistance_2w, resistance_4w: slow (10 PLC, default, most accurate), medium (1 PLC), fast (0.3 PLC). sensor: Required for temperature: pt100 (RTD) or thermocouple type B, E, J, K, N, R, S or T. Input parameters: - `count` (integer) - `function` - `range` - `sensor` - `speed` ### `get_device_info` (~25 tokens) Instrument model, serial number, firmware, VISA resource and the present measurement configuration. ## Diagnostics Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/shaag7967-mcp-server-siglent-sdm3045x/mcp-server-siglent-sdm3045x#diagnostics ## Score history - 2026-11-05: 79 - 2026-11-04: 63 - 2026-11-03: 63 - 2026-11-02: 77 - 2026-11-01: 77 - 2026-10-31: 76 - 2026-10-30: 61 - 2026-10-29: 60 - 2026-10-28: 75 ## Common questions ### What is the Siglent SDM3045X multimeter MCP server? Siglent SDM3045X multimeter is an MCP server listed in the public MCP registry as io.github.shaag7967/mcp-server-siglent-sdm3045x. Measurements with a Siglent SDM3045X bench multimeter via USB or LAN (unofficial). This page covers its PyPI package (mcp-server-siglent-sdm3045x). ### Is the Siglent SDM3045X multimeter MCP server safe to use? Siglent SDM3045X multimeter scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Siglent SDM3045X multimeter MCP server expose? Siglent SDM3045X multimeter exposes 5 tools: read, measure, sample, burst, get_device_info. Their descriptions and schemas cost roughly 1,515 tokens of context every time the server is loaded. ### Is the Siglent SDM3045X multimeter MCP server still maintained? Siglent SDM3045X multimeter is still listed as active in the MCP registry. We last reached this channel on 5 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 Siglent SDM3045X multimeter MCP server under? Siglent SDM3045X multimeter declares the MIT 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/mcp-server-siglent-sdm3045x/ - Socket report: https://socket.dev/pypi/package/mcp-server-siglent-sdm3045x - Repository: https://github.com/shaag7967/mcp-server-siglent-sdm3045x - Changelog RSS feed: https://verifymcp.io/servers/shaag7967-mcp-server-siglent-sdm3045x/mcp-server-siglent-sdm3045x.xml - Changelog JSON feed: https://verifymcp.io/servers/shaag7967-mcp-server-siglent-sdm3045x/mcp-server-siglent-sdm3045x.json - HTML version of this page: https://verifymcp.io/servers/shaag7967-mcp-server-siglent-sdm3045x/mcp-server-siglent-sdm3045x