Bench DC Power Supply
PYPI · LABMCP-BENCH-PSU · SCANNED SEP 30
MCP server for programmable DC bench power supplies from Rigol, Siglent and Aim-TTi.
Available components
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 17 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 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1180 tokens (~98/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the Bench DC Power Supply MCP server?
Bench DC Power Supply runs locally as a PyPI package, launched with uvx labmcp-bench-psu. 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-bench-psu
claude mcp add k-dense-ai-labmcp-bench-psu -- uvx labmcp-bench-psu
{
"mcpServers": {
"k-dense-ai-labmcp-bench-psu": {
"command": "uvx",
"args": [
"labmcp-bench-psu"
]
}
}
} {
"servers": {
"k-dense-ai-labmcp-bench-psu": {
"command": "uvx",
"args": [
"labmcp-bench-psu"
]
}
}
} codex mcp add k-dense-ai-labmcp-bench-psu -- uvx labmcp-bench-psu
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"k-dense-ai-labmcp-bench-psu": {
"type": "local",
"command": [
"uvx",
"labmcp-bench-psu"
],
"enabled": true
}
}
} openclaw mcp add k-dense-ai-labmcp-bench-psu --command uvx --arg labmcp-bench-psu
mcp_servers:
k-dense-ai-labmcp-bench-psu:
command: "uvx"
args: ["labmcp-bench-psu"] {
"McpServers": {
"k-dense-ai-labmcp-bench-psu": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"labmcp-bench-psu"
]
}
}
} assistant mcp add k-dense-ai-labmcp-bench-psu -t stdio -c uvx -a labmcp-bench-psu
{
"mcpServers": {
"k-dense-ai-labmcp-bench-psu": {
"command": "uvx",
"args": [
"labmcp-bench-psu"
]
}
}
} 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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 92 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- Package version: 0.1.2 → 0.1.3 functional
- 26 Sept 26 39
First indexed and scored.
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 30 Sept 2026 · Analysed pypi/labmcp-bench-psu@0.1.3
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-bench-psu-v0.1.3 |
| Rekor log index | 2969517815 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:1a8ec3af1ea2707295e1c0aba6f3594a4e7c4382514aea834572297f54957102 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 17 packages
| Packages resolved | 17 |
|---|---|
| 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 →
all_outputs_off All Outputs Off ~39
Switch every output OFF (emergency stop for the whole supply). Each channel is switched individually and read back where the instrument supports it.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| all_off_confirmed | boolean | yes | – |
| outputs | array | yes | – |
| problems | array | yes | – |
No examples provided.
clear_protection_trip Clear Protection Trip ~70
Clear an OVP/OCP trip after fixing its cause. The output stays OFF; use `output_on` to re-energise. On Aim-TTi supplies this clears trips on all outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | Output channel number (1 = CH1 / output 1) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | 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_errors Get Errors ~28
Read (and clear) the instrument's error queue / error registers. Empty list = no errors.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_outputs Get Outputs ~61
Report each channel: voltage and current-limit setpoints, measured voltage/current/power, output on/off, CV/CC mode, and OVP/OCP levels and trip state where the model supports them.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | – | – | One channel, or omit for all |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
output_off Output Off ~41
Switch a channel's output OFF. Safe to call at any time.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | Output channel number (1 = CH1 / output 1) |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| max_current_a | – | yes | – |
| max_voltage_v | – | yes | Highest settable voltage on this channel (model table) |
| measured_current_a | – | yes | – |
| measured_power_w | – | yes | – |
| measured_voltage_v | – | yes | – |
| mode | – | yes | 'CV', 'CC' or 'UR' (unregulated); None when off or unknown |
| mode_source | – | yes | 'instrument' or 'inferred' (from readback vs setpoints) |
| notes | array | – | – |
| ocp_a | – | – | – |
| ocp_enabled | – | – | – |
| ocp_tripped | – | – | – |
| output_on | – | yes | Output state (None if the instrument cannot report it) |
| ovp_enabled | – | – | – |
| ovp_tripped | – | – | – |
| ovp_v | – | – | – |
| set_current_a | – | yes | Current limit setpoint |
| set_voltage_v | – | yes | – |
| timestamp | string | yes | UTC time of the readings (ISO 8601) |
No examples provided.
output_on Output On ~76
Switch a channel's output ON, energising the connected load at the present setpoints. The setpoints are read back first and the output is refused if they exceed the safety limits (e.g. after someone changed them on the front panel).
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | Output channel number (1 = CH1 / output 1) |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| max_current_a | – | yes | – |
| max_voltage_v | – | yes | Highest settable voltage on this channel (model table) |
| measured_current_a | – | yes | – |
| measured_power_w | – | yes | – |
| measured_voltage_v | – | yes | – |
| mode | – | yes | 'CV', 'CC' or 'UR' (unregulated); None when off or unknown |
| mode_source | – | yes | 'instrument' or 'inferred' (from readback vs setpoints) |
| notes | array | – | – |
| ocp_a | – | – | – |
| ocp_enabled | – | – | – |
| ocp_tripped | – | – | – |
| output_on | – | yes | Output state (None if the instrument cannot report it) |
| ovp_enabled | – | – | – |
| ovp_tripped | – | – | – |
| ovp_v | – | – | – |
| set_current_a | – | yes | Current limit setpoint |
| set_voltage_v | – | yes | – |
| timestamp | string | yes | UTC time of the readings (ISO 8601) |
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.
set_current_limit Set Current Limit ~78
Set a channel's current limit (the constant-current setpoint). Refused above `max_current_a` (checked even with the output off) or above the channel's range.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | Output channel number (1 = CH1 / output 1) |
| current_a | number | yes | Current-limit setpoint in A |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| max_current_a | – | yes | – |
| max_voltage_v | – | yes | Highest settable voltage on this channel (model table) |
| measured_current_a | – | yes | – |
| measured_power_w | – | yes | – |
| measured_voltage_v | – | yes | – |
| mode | – | yes | 'CV', 'CC' or 'UR' (unregulated); None when off or unknown |
| mode_source | – | yes | 'instrument' or 'inferred' (from readback vs setpoints) |
| notes | array | – | – |
| ocp_a | – | – | – |
| ocp_enabled | – | – | – |
| ocp_tripped | – | – | – |
| output_on | – | yes | Output state (None if the instrument cannot report it) |
| ovp_enabled | – | – | – |
| ovp_tripped | – | – | – |
| ovp_v | – | – | – |
| set_current_a | – | yes | Current limit setpoint |
| set_voltage_v | – | yes | – |
| timestamp | string | yes | UTC time of the readings (ISO 8601) |
No examples provided.
set_protection Set Protection ~154
Set over-voltage (OVP) and/or over-current (OCP) protection for a channel. When exceeded, the supply switches the output off. Rigol: levels + on/off; Aim-TTi CPX/QL/PL-P: levels (always armed), MX: levels + on/off; Siglent SPD1000X: levels only; SPD3303X: not available.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | Output channel number (1 = CH1 / output 1) |
| enabled | – | – | Switch OVP/OCP on or off (models that allow it) |
| ocp_a | – | – | Over-current trip level in A |
| ovp_v | – | – | Over-voltage trip level in V |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| notes | array | yes | – |
| ocp_a | – | yes | – |
| ocp_enabled | – | yes | – |
| ocp_tripped | – | yes | – |
| ovp_enabled | – | yes | – |
| ovp_tripped | – | yes | – |
| ovp_v | – | yes | – |
No examples provided.
set_voltage Set Voltage ~93
Set a channel's voltage setpoint. Refused above `max_voltage_v` (checked even with the output off) or above the channel's range. If the output is on, the load sees the new voltage at once.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | Output channel number (1 = CH1 / output 1) |
| voltage_v | number | yes | Voltage setpoint in V (negative only on negative channels) |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| max_current_a | – | yes | – |
| max_voltage_v | – | yes | Highest settable voltage on this channel (model table) |
| measured_current_a | – | yes | – |
| measured_power_w | – | yes | – |
| measured_voltage_v | – | yes | – |
| mode | – | yes | 'CV', 'CC' or 'UR' (unregulated); None when off or unknown |
| mode_source | – | yes | 'instrument' or 'inferred' (from readback vs setpoints) |
| notes | array | – | – |
| ocp_a | – | – | – |
| ocp_enabled | – | – | – |
| ocp_tripped | – | – | – |
| output_on | – | yes | Output state (None if the instrument cannot report it) |
| ovp_enabled | – | – | – |
| ovp_tripped | – | – | – |
| ovp_v | – | – | – |
| set_current_a | – | yes | Current limit setpoint |
| set_voltage_v | – | yes | – |
| timestamp | string | yes | UTC time of the readings (ISO 8601) |
No examples provided.
What is the Bench DC Power Supply MCP server?
Bench DC Power Supply is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-bench-psu. MCP server for programmable DC bench power supplies from Rigol, Siglent and Aim-TTi. This page covers its PyPI package (labmcp-bench-psu).
Is the Bench DC Power Supply MCP server safe to use?
Bench DC Power Supply scores 69 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 Bench DC Power Supply MCP server expose?
Bench DC Power Supply exposes 12 tools: get_connection_info, get_command_log, reconnect, get_outputs, set_voltage, and 7 more. Their descriptions and schemas cost roughly 761 tokens of context every time the server is loaded.
Is the Bench DC Power Supply MCP server still maintained?
Bench DC Power Supply 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 Bench DC Power Supply MCP server under?
Bench DC Power Supply 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.