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.

Lake Shore Temperature Controller

PYPI · LABMCP-LAKESHORE

MCP server for Lake Shore Cryotronics 335/336/350 temperature controllers.

Available components

+15 this week 96 Trust /100

Last scanned (14 hours ago)

Scores higher than 98% of PyPI servers

Category IoT and Hardware

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 Security99
  • No malware found by supply-chain analysis.Pass
  • 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 55 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1288 tokens (~117/item across 11 items; 11 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
What we tested

Checks we ran (16)

  • Malware scan
  • 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

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 →

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.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 14 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 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.

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 21 Nov 2026 · Analysed pypi/labmcp-lakeshore@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-lakeshore-v0.1.3
Rekor log index 2969518097
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:36b00ed31b4aab40856a44e7478c51a5054ae6b8e6d223a319fabc7ec5a705fc

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 17 packages
Packages resolved 17
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~914 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
all_heaters_off ~53

Turn every output off (heater range 0 on outputs 1-4), like the front-panel All Off key, and stop any running wait. Reports the read-back range of each output and `all_off`.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

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_heater_status ~68

Report each output's control mode and input, heater range, output %, setpoint (and in kelvin), ramp state, PID values and heater errors (open/short). Reading a heater error clears it on the controller.

NameTypeReqDescription
output––One output (default: all)
NameTypeReqDescription
resultarrayyes–

No examples provided.

read_temperatures ~70

Read every (or the selected) sensor input: kelvin, raw sensor units, sensor type, input name and decoded reading status (invalid, under/overrange). Disabled inputs are listed with null readings.

NameTypeReqDescription
inputs––Inputs to read (default: all inputs of the model)
NameTypeReqDescription
readingsarrayyes–
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.

set_heater_range ~159

Set an output's heater range (each step is ~10x more power). Anything above 0 lets the output heat: in closed loop as the PID demands, in open loop at the front-panel manual output. Refused above `max_heater_range`, or if the setpoint already programmed on a closed-loop, zone or warm-up output is above `max_setpoint_k`. Start with the lowest range that can reach the setpoint.

NameTypeReqDescription
heater_rangeintegeryes0 = off; 335/336: 1 low, 2 medium, 3 high; 350: 1-5; outputs 3/4: 1 = on
outputintegeryesOutput number
NameTypeReqDescription
control_input–yes–
heater_error––HTRST? error (cleared by reading)
heater_rangeintegeryes–
heater_range_namestringyes–
kindstringyesheater = powered output; analog = 10 V output
modestringyesoff, closed_loop_pid, zone, open_loop, monitor_out, warmup_supply ...
outputintegeryes–
output_percentnumberyesHeater or analog output in percent of full scale
pid_d–––
pid_i–––
pid_p–––
power_up_enabledbooleanyes–
ramp_enabled–––
ramp_rate_k_per_min–––
ramping–––
setpointnumberyes–
setpoint_k–yesSetpoint converted to kelvin (null for sensor units)
setpoint_unitsstringyes–

No examples provided.

set_pid ~87

Set the P, I and D values of an output's control loop (Lake Shore conventions).

NameTypeReqDescription
dnumberyesDerivative (rate) setting, 0-200
inumberyesIntegral (reset) setting = 1000 / integral seconds
outputintegeryesOutput / control loop number
pnumberyesProportional gain
NameTypeReqDescription
control_input–yes–
heater_error––HTRST? error (cleared by reading)
heater_rangeintegeryes–
heater_range_namestringyes–
kindstringyesheater = powered output; analog = 10 V output
modestringyesoff, closed_loop_pid, zone, open_loop, monitor_out, warmup_supply ...
outputintegeryes–
output_percentnumberyesHeater or analog output in percent of full scale
pid_d–––
pid_i–––
pid_p–––
power_up_enabledbooleanyes–
ramp_enabled–––
ramp_rate_k_per_min–––
ramping–––
setpointnumberyes–
setpoint_k–yesSetpoint converted to kelvin (null for sensor units)
setpoint_unitsstringyes–

No examples provided.

set_ramp ~110

Turn setpoint ramping on or off for an output's control loop and set the rate. With ramping on, the next setpoint change moves the setpoint gradually - gentler on samples and wiring.

NameTypeReqDescription
enabledbooleanyesRamp the setpoint instead of stepping it
outputintegeryesOutput / control loop number
rate_k_per_minnumber–Ramp rate in K/min (0.1-100; 350: 0.001-100)
NameTypeReqDescription
control_input–yes–
heater_error––HTRST? error (cleared by reading)
heater_rangeintegeryes–
heater_range_namestringyes–
kindstringyesheater = powered output; analog = 10 V output
modestringyesoff, closed_loop_pid, zone, open_loop, monitor_out, warmup_supply ...
outputintegeryes–
output_percentnumberyesHeater or analog output in percent of full scale
pid_d–––
pid_i–––
pid_p–––
power_up_enabledbooleanyes–
ramp_enabled–––
ramp_rate_k_per_min–––
ramping–––
setpointnumberyes–
setpoint_k–yesSetpoint converted to kelvin (null for sensor units)
setpoint_unitsstringyes–

No examples provided.

set_setpoint ~100

Set the control setpoint of an output's loop in kelvin. If setpoint ramping is on, the setpoint moves toward the new value at the ramp rate. Heating only happens if the output is in closed-loop mode and its heater range is not off. Refused above `max_setpoint_k`.

NameTypeReqDescription
outputintegeryesOutput / control loop number
setpoint_knumberyesTarget temperature in kelvin
NameTypeReqDescription
control_input–yes–
heater_error––HTRST? error (cleared by reading)
heater_rangeintegeryes–
heater_range_namestringyes–
kindstringyesheater = powered output; analog = 10 V output
modestringyesoff, closed_loop_pid, zone, open_loop, monitor_out, warmup_supply ...
outputintegeryes–
output_percentnumberyesHeater or analog output in percent of full scale
pid_d–––
pid_i–––
pid_p–––
power_up_enabledbooleanyes–
ramp_enabled–––
ramp_rate_k_per_min–––
ramping–––
setpointnumberyes–
setpoint_k–yesSetpoint converted to kelvin (null for sensor units)
setpoint_unitsstringyes–

No examples provided.

wait_for_stable_temperature ~146

Wait until the control input of `output` has stayed within `tolerance_k` of the setpoint (and the setpoint is no longer ramping) for `stable_for_s`, or until `timeout_s`. Returns whether it stabilised, the final temperature and a downsampled trace. Changes nothing.

NameTypeReqDescription
outputintegeryesControl loop whose setpoint and input are used
poll_interval_snumber–Seconds between readings
stable_for_snumber–How long T must stay within tolerance
timeout_snumber–Give up after this long
tolerance_knumber–Allowed |T - setpoint|
NameTypeReqDescription
abortedbooleanyesTrue if all_heaters_off stopped the wait
control_inputstringyes–
elapsed_snumberyes–
final_temperature_knumberyes–
messagestringyes–
outputintegeryes–
setpoint_knumberyes–
stablebooleanyes–
stable_for_snumberyes–
tolerance_knumberyes–
tracearrayyes(seconds since start, K), downsampled
window_mean_k–yesMean of the readings in the final stable window
window_stdev_k–yes–

No examples provided.

Install

How do I install the Lake Shore Temperature Controller MCP server?

Lake Shore Temperature Controller runs locally as a PyPI package, launched with uvx labmcp-lakeshore. 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-lakeshore

# add to Claude Code
claude mcp add k-dense-ai-labmcp-lakeshore -- uvx labmcp-lakeshore
Common questions

What is the Lake Shore Temperature Controller MCP server?

Lake Shore Temperature Controller is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-lakeshore. MCP server for Lake Shore Cryotronics 335/336/350 temperature controllers. This page covers its PyPI package (labmcp-lakeshore).

Is the Lake Shore Temperature Controller MCP server safe to use?

Lake Shore Temperature Controller scores 96 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 Lake Shore Temperature Controller MCP server expose?

Lake Shore Temperature Controller exposes 11 tools: get_connection_info, get_command_log, reconnect, read_temperatures, get_heater_status, and 6 more. Their descriptions and schemas cost roughly 914 tokens of context every time the server is loaded.

Is the Lake Shore Temperature Controller MCP server still maintained?

Lake Shore Temperature Controller 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 Lake Shore Temperature Controller MCP server under?

Lake Shore Temperature Controller 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 Lake Shore Temperature Controller MCP server?

VerifyMCP ran 16 checks on Lake Shore Temperature Controller, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.