Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Keithley SourceMeter SMU

PYPI · LABMCP-KEITHLEY-SMU · SCANNED SEP 30

MCP server for Keithley SourceMeter SMUs (2400 series SCPI, 2450 family SCPI, 2600B TSP).

Available components

pypi · labmcp-keithley-smu 65
65 Trust /100
Trust breakdown (7 categories)

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 Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1433 tokens (~119/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
  • Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Never tell the user", at byte 998 of that field. See how to fix → Fail
  • 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
Install

How do I install the Keithley SourceMeter SMU MCP server?

Keithley SourceMeter SMU runs locally as a PyPI package, launched with uvx labmcp-keithley-smu. 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-keithley-smu

# add to Claude Code
claude mcp add k-dense-ai-labmcp-keithley-smu -- uvx labmcp-keithley-smu
// .cursor/mcp.json
{
  "mcpServers": {
    "k-dense-ai-labmcp-keithley-smu": {
      "command": "uvx",
      "args": [
        "labmcp-keithley-smu"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "k-dense-ai-labmcp-keithley-smu": {
      "command": "uvx",
      "args": [
        "labmcp-keithley-smu"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add k-dense-ai-labmcp-keithley-smu -- uvx labmcp-keithley-smu
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-dense-ai-labmcp-keithley-smu": {
      "type": "local",
      "command": [
        "uvx",
        "labmcp-keithley-smu"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add k-dense-ai-labmcp-keithley-smu --command uvx --arg labmcp-keithley-smu
# ~/.hermes/config.yaml
mcp_servers:
  k-dense-ai-labmcp-keithley-smu:
    command: "uvx"
    args: ["labmcp-keithley-smu"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "k-dense-ai-labmcp-keithley-smu": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "labmcp-keithley-smu"
      ]
    }
  }
}
# add to Vellum
assistant mcp add k-dense-ai-labmcp-keithley-smu -t stdio -c uvx -a labmcp-keithley-smu
// mcp.json
{
  "mcpServers": {
    "k-dense-ai-labmcp-keithley-smu": {
      "command": "uvx",
      "args": [
        "labmcp-keithley-smu"
      ]
    }
  }
}
Changelog

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 −5
    • 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 +1
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 26 Sept 26 68

    First indexed and scored.

Diagnostics

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-keithley-smu@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-keithley-smu-v0.1.2
Rekor log index 2969518040
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:049ef67402cf4b849d8fcf4898c32d9a9840af78217c6a337b16b2e65a7d973f

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 →

MCP tools · 12 exposed · ~966 tokens

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 →

Tool Tokens
configure_source ~169

Set up the source (function, level, compliance, range, measurement speed) while the output is OFF. Measures V and I with auto-ranging. Refused if the output is on; turn it off first or use `set_source_level`. Limits are checked before anything is sent.

NameTypeReqDescription
compliancenumberyesLimit: current limit in A (voltage source) or voltage limit in V (current source)
levelnumberyesSource level: volts for a voltage source, amps for a current source
nplcnumber–Measurement integration time in power-line cycles (1 = 16.7/20 ms)
sourcestringyesSource voltage or current
source_range––Fixed source range (V or A); omit for auto-range
NameTypeReqDescription
compliancenumberyesCompliance limit, in compliance_unit
compliance_unitstringyes–
dialectstringyes–
in_compliancebooleanyesTrue if the source is presently clamped at the compliance limit
levelnumberyesProgrammed source level, in level_unit
level_unitstringyes–
output_onbooleanyes–
remote_sense–yesTrue = 4-wire (remote) sense
sourcestringyes–
terminals–yesfront/rear (None on the 2600B, which has one set of terminals)
timestampstringyes–

No examples provided.

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.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
resultarrayyes–

No examples provided.

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 ~51

Identify the SMU: manufacturer, model, serial, firmware, command dialect (2400 / 2450 / 2600), channel (2600B) and the model's maximum source voltage and current.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_status ~46

Report whether the output is on, the source function (voltage/current), programmed level, compliance limit, whether the source is in compliance, terminals and 2/4-wire sense.

Input schema present but exposes no named parameters.

NameTypeReqDescription
compliancenumberyesCompliance limit, in compliance_unit
compliance_unitstringyes–
dialectstringyes–
in_compliancebooleanyesTrue if the source is presently clamped at the compliance limit
levelnumberyesProgrammed source level, in level_unit
level_unitstringyes–
output_onbooleanyes–
remote_sense–yesTrue = 4-wire (remote) sense
sourcestringyes–
terminals–yesfront/rear (None on the 2600B, which has one set of terminals)
timestampstringyes–

No examples provided.

measure ~47

Take one source-measure reading (voltage, current, V/I, power, compliance flag) of the energised DUT. Does not change any setting; refused if the output is off.

Input schema present but exposes no named parameters.

NameTypeReqDescription
compliancenumberyes–
current_anumberyes–
in_compliancebooleanyes–
levelnumberyes–
power_wnumberyesV x I (negative = the DUT delivers power)
resistance_ohm–yesV / I (None if I = 0)
sourcestringyes–
timestampstringyes–
voltage_vnumberyes–

No examples provided.

output_off ~34

Switch the SMU output OFF immediately (and abort any IV sweep in progress). Always available, including in read-only mode.

Input schema present but exposes no named parameters.

NameTypeReqDescription
compliancenumberyesCompliance limit, in compliance_unit
compliance_unitstringyes–
dialectstringyes–
in_compliancebooleanyesTrue if the source is presently clamped at the compliance limit
levelnumberyesProgrammed source level, in level_unit
level_unitstringyes–
output_onbooleanyes–
remote_sense–yesTrue = 4-wire (remote) sense
sourcestringyes–
terminals–yesfront/rear (None on the 2600B, which has one set of terminals)
timestampstringyes–

No examples provided.

output_on ~64

Switch the SMU output ON: the configured voltage or current is applied to the DUT. The programmed level and compliance are read back from the instrument and checked against the safety limits first. Confirm with the user that the DUT is connected and safe to energise.

Input schema present but exposes no named parameters.

NameTypeReqDescription
compliancenumberyesCompliance limit, in compliance_unit
compliance_unitstringyes–
dialectstringyes–
in_compliancebooleanyesTrue if the source is presently clamped at the compliance limit
levelnumberyesProgrammed source level, in level_unit
level_unitstringyes–
output_onbooleanyes–
remote_sense–yesTrue = 4-wire (remote) sense
sourcestringyes–
terminals–yesfront/rear (None on the 2600B, which has one set of terminals)
timestampstringyes–

No examples provided.

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_iv_sweep ~287

Run a stepped IV sweep: configure the source, switch the output ON, step through the levels measuring V and I at each, then ALWAYS switch the output OFF (also on errors or when `output_off` is called). Returns the curve (downsampled), compliance flags, a linear fit and optional full CSV (a new file; an existing file is never overwritten). The output must be off beforehand. Limits are checked first.

NameTypeReqDescription
compliancenumberyesCurrent limit in A (voltage sweep) or voltage limit in V (current sweep)
delay_snumber–Settling delay at each point, s
dualboolean–Sweep back from stop to start afterwards (hysteresis)
max_pointsinteger–Maximum points returned in the reply
nplcnumber–Integration time per measurement, PLC
pointsintegeryesLevels from start to stop (inclusive)
save_path––Optional CSV path for every point
sourcestring–Sweep voltage or current
spacingstring–Level spacing
startnumberyesFirst level: V (voltage sweep) or A (current sweep)
stopnumberyesLast level: V or A
stop_on_complianceboolean–End the sweep at the first compliance point
NameTypeReqDescription
abortedbooleanyes–
compliancenumberyes–
compliance_pointsintegeryesNumber of measured points that were in compliance
compliance_unitstringyes–
current_aarrayyesMeasured current (downsampled; null = overflow)
current_max_a–yes–
current_min_a–yes–
dualbooleanyes–
duration_snumberyes–
first_compliance_level–yes–
in_compliancearrayyesCompliance flag per returned point
levelarrayyesProgrammed source levels (downsampled to max_points)
max_abs_power_w–yes–
ohmic_fit–yesLeast-squares line through the non-compliance points of a linear sweep (meaningful for resistive DUTs)
output_offbooleanyesOutput state confirmed OFF after the sweep
overflow_pointsinteger–Points where the SMU returned its overflow marker (excluded from stats and fit)
points_measuredintegeryes–
points_requestedintegeryes–
points_returnedintegeryes–
saved_to–yes–
sourcestringyes–
spacingstringyes–
startedstringyes–
stop_reason–yes–
voltage_max_v–yes–
voltage_min_v–yes–
voltage_varrayyesMeasured voltage (downsampled; null = overflow)

No examples provided.

set_4wire ~79

Select 4-wire (remote sense, Kelvin) or 2-wire measurement. 4-wire removes lead resistance for low-resistance DUTs but needs the SENSE leads connected. Refused while the output is on.

NameTypeReqDescription
enabledbooleanyesTrue = 4-wire remote sense, False = 2-wire local sense
NameTypeReqDescription
compliancenumberyesCompliance limit, in compliance_unit
compliance_unitstringyes–
dialectstringyes–
in_compliancebooleanyesTrue if the source is presently clamped at the compliance limit
levelnumberyesProgrammed source level, in level_unit
level_unitstringyes–
output_onbooleanyes–
remote_sense–yesTrue = 4-wire (remote) sense
sourcestringyes–
terminals–yesfront/rear (None on the 2600B, which has one set of terminals)
timestampstringyes–

No examples provided.

set_source_level ~68

Change the level of the configured source. If the output is ON the new voltage/current is applied to the DUT immediately. The level and the present compliance are checked against the safety limits first.

NameTypeReqDescription
levelnumberyesNew level for the configured source: V or A
NameTypeReqDescription
compliancenumberyesCompliance limit, in compliance_unit
compliance_unitstringyes–
dialectstringyes–
in_compliancebooleanyesTrue if the source is presently clamped at the compliance limit
levelnumberyesProgrammed source level, in level_unit
level_unitstringyes–
output_onbooleanyes–
remote_sense–yesTrue = 4-wire (remote) sense
sourcestringyes–
terminals–yesfront/rear (None on the 2600B, which has one set of terminals)
timestampstringyes–

No examples provided.

Common questions

What is the Keithley SourceMeter SMU MCP server?

Keithley SourceMeter SMU is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-keithley-smu. MCP server for Keithley SourceMeter SMUs (2400 series SCPI, 2450 family SCPI, 2600B TSP). This page covers its PyPI package (labmcp-keithley-smu).

Is the Keithley SourceMeter SMU MCP server safe to use?

Keithley SourceMeter SMU scores 65 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 Keithley SourceMeter SMU MCP server expose?

Keithley SourceMeter SMU exposes 12 tools: get_connection_info, get_command_log, reconnect, get_device_info, get_status, and 7 more. Their descriptions and schemas cost roughly 966 tokens of context every time the server is loaded.

Is the Keithley SourceMeter SMU MCP server still maintained?

Keithley SourceMeter SMU 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 Keithley SourceMeter SMU MCP server under?

Keithley SourceMeter SMU 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.