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.

JULABO Circulator

PYPI · LABMCP-JULABO

MCP server for JULABO heating and refrigerated circulators (CORIO, MAGIO, DYNEO).

Available components

0 this week 81 Trust /100

Last scanned (18 hours ago)

Scores higher than 80% 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 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 55 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1043 tokens (~104/item across 10 items; 10 tools + 0 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 Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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 (15)

  • 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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

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.

  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 11 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 −2
    • Stability: pass → 0.87 functional
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-julabo@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-julabo-v0.1.2
Rekor log index 2969517481
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:5d830c7bcd555c55aa785fb71deb45ba391aead93258f6edc0d7bfe76d7c80a3

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 · 10 exposed · ~663 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
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_setpoint ~22

Read the current temperature setpoint and whether temperature control is running.

Input schema present but exposes no named parameters.

NameTypeReqDescription
runningbooleanyes–
setpoint_cnumberyesSetpoint read back from the circulator
statusstringyes–
timestampstringyes–

No examples provided.

get_status ~56

Report the circulator's status message (decoded: operating state, rejected command or alarm), whether temperature control is running, the setpoint, the device's own excess-temperature protection setting and warning limits, and the firmware version.

Input schema present but exposes no named parameters.

NameTypeReqDescription
bath_temperature_cnumberyes–
codeintegeryesStatus code: 00-03 operating state, negative = alarm or rejected command
excess_temperature_protection_cnumberyesSetting of the high-temperature safety function on the device (in_pv_04)
firmwarestringyes–
high_warning_limit_c––in_sp_03; not available on CORIO CD
kindstringyes–
low_warning_limit_c––in_sp_04; not available on CORIO CD
meaningstringyes–
messagestringyesStatus text sent by the circulator
remote_control–yesTrue if remote control is enabled (None during alarms)
runningbooleanyesTemperature control started (in_mode_05)
setpoint_cnumberyes–
timestampstringyes–

No examples provided.

read_temperatures ~64

Read the bath temperature, the heating/cooling power in % and the safety-sensor temperature, and optionally the external Pt100 sensor.

NameTypeReqDescription
include_externalboolean–Also read the external Pt100 sensor (MAGIO/DYNEO; not CORIO)
NameTypeReqDescription
bath_temperature_cnumberyesActual bath / internal temperature (in_pv_00)
external_temperature_c––External Pt100 sensor (in_pv_02); None if not requested or not available (CORIO)
heating_power_pctnumberyesActuating variable in %; negative = cooling (in_pv_01)
safety_sensor_temperature_cnumberyesHigh-temperature safety sensor (in_pv_03)
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_setpoint ~94

Set the circulator's temperature setpoint (out_sp_00). If temperature control is running, the circulator starts heating or cooling to it immediately. Refused outside `min_temperature_c`..`max_temperature_c`; the circulator itself also rejects values outside its range or warning limits (reported as an error). Needs remote control enabled.

NameTypeReqDescription
temperature_cnumberyesNew setpoint in °C
NameTypeReqDescription
runningbooleanyes–
setpoint_cnumberyesSetpoint read back from the circulator
statusstringyes–
timestampstringyes–

No examples provided.

start_circulation ~78

Start temperature control (out_mode_05 1): the pump runs and the bath heats or cools to the setpoint, which is checked against the safety limits first (it may have been changed on the front panel). Make sure the bath is filled and any external hoses are connected and secured. Needs remote control enabled.

Input schema present but exposes no named parameters.

NameTypeReqDescription
runningbooleanyes–
setpoint_cnumberyesSetpoint read back from the circulator
statusstringyes–
timestampstringyes–

No examples provided.

stop_circulation ~50

Stop temperature control and the pump (out_mode_05 0), then confirm with in_mode_05. Also ends a running `wait_for_temperature`. The bath stays hot/cold after stopping.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

wait_for_temperature ~178

Poll the bath (or external) temperature until it has been within `tolerance_c` of the target for `stable_for_s` seconds, or `timeout_s` passes. Does not change anything; start circulation first. Stops early (reached = false) if the circulator raises an alarm or a stop command is sent. Returns a short temperature trace.

NameTypeReqDescription
poll_interval_snumber–Seconds between readings
sensorstring–'external' = Pt100 sensor (MAGIO/DYNEO)
stable_for_snumber–Must stay within tolerance this long
target_c––Temperature to wait for; default: the current setpoint
timeout_snumber–Give up after this many seconds
tolerance_cnumber–Accepted deviation in °C
NameTypeReqDescription
abortedbooleanyesTrue if a stop command or an alarm ended the wait early
elapsed_snumberyes–
final_temperature_cnumberyes–
messagestringyes–
reachedbooleanyes–
sensorstringyes–
target_cnumberyes–
tolerance_cnumberyes–
tracearrayyes(seconds since start, °C), at most ~30 points

No examples provided.

Install

How do I install the JULABO Circulator MCP server?

JULABO Circulator runs locally as a PyPI package, launched with uvx labmcp-julabo. 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-julabo

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

What is the JULABO Circulator MCP server?

JULABO Circulator is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-julabo. MCP server for JULABO heating and refrigerated circulators (CORIO, MAGIO, DYNEO). This page covers its PyPI package (labmcp-julabo).

Is the JULABO Circulator MCP server safe to use?

JULABO Circulator scores 81 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 JULABO Circulator MCP server expose?

JULABO Circulator exposes 10 tools: get_connection_info, get_command_log, reconnect, read_temperatures, get_status, and 5 more. Their descriptions and schemas cost roughly 663 tokens of context every time the server is loaded.

Is the JULABO Circulator MCP server still maintained?

JULABO Circulator 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 JULABO Circulator MCP server under?

JULABO Circulator 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 JULABO Circulator MCP server?

VerifyMCP ran 15 checks on JULABO Circulator, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about JULABO Circulator: Malware scan. 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.