Tecan Cavro Syringe Pump
PYPI · LABMCP-CAVRO
MCP server for Tecan Cavro syringe pumps (XLP 6000, XMP 6000, XCalibur) over the DT protocol.
Available components
Last scanned (20 hours ago)
Scores higher than 78% of PyPI servers
Category IoT and Hardware
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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1077 tokens (~119/item across 9 items; 9 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
- 94% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 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
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 →
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
- 17 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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-cavro@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-cavro-v0.1.3 |
| Rekor log index | 2969517078 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:9d01c4640f8167f33390febcee1c02d45126c81a56a5d7003df5f843b0b10d59 |
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 →
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 →
aspirate_ul Aspirate Ul ~116
Draw `volume_ul` into the syringe at `flow_ul_s` through the current (or given) valve port, and wait until the move has finished. The pump must be initialized and have room for the volume.
| Name | Type | Req | Description |
|---|---|---|---|
| flow_ul_s | number | – | Plunger flow rate, µL/s |
| port | – | – | Distribution valves: port to turn to first |
| valve | – | – | Turn the valve here first (e.g. 'input') |
| volume_ul | number | yes | Volume to draw into the syringe, µL |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| duration_s | number | yes | – |
| flow_ul_s | number | yes | Flow at the commanded top speed (ramps make the average slightly lower) |
| moved_ul | number | yes | Volume actually commanded after rounding to whole plunger steps |
| plunger_position_ul | number | yes | – |
| requested_ul | number | yes | – |
| steps | integer | yes | – |
| terminated | boolean | yes | True if `terminate` interrupted the move |
| timestamp | string | yes | – |
| top_speed_pulses_s | integer | yes | – |
| valve_position | string | yes | – |
No examples provided.
dispense_ul Dispense Ul ~114
Push `volume_ul` out of the syringe at `flow_ul_s` through the current (or given) valve port, and wait until the move has finished. The syringe must contain at least that volume.
| Name | Type | Req | Description |
|---|---|---|---|
| flow_ul_s | number | – | Plunger flow rate, µL/s |
| port | – | – | Distribution valves: port to turn to first |
| valve | – | – | Turn the valve here first (e.g. 'output') |
| volume_ul | number | yes | Volume to push out of the syringe, µL |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| duration_s | number | yes | – |
| flow_ul_s | number | yes | Flow at the commanded top speed (ramps make the average slightly lower) |
| moved_ul | number | yes | Volume actually commanded after rounding to whole plunger steps |
| plunger_position_ul | number | yes | – |
| requested_ul | number | yes | – |
| steps | integer | yes | – |
| terminated | boolean | yes | True if `terminate` interrupted the move |
| timestamp | string | yes | – |
| top_speed_pulses_s | integer | yes | – |
| valve_position | 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_status Get Status ~45
Report whether the pump is ready or busy, any error (decoded), the plunger position as the volume in the syringe, the valve position, resolution mode and current top speed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | yes | Meaning of the error code |
| error_code | integer | yes | Error code from the status byte (0 = none) |
| plunger_position_steps | integer | yes | – |
| plunger_position_ul | number | yes | Volume currently drawn into the syringe |
| ready | boolean | yes | True when the pump accepts new move commands (Q status bit 5) |
| resolution_mode | integer | yes | 0 = standard (N0), 1 = fine positioning (N1), 2 = microstep (N2) |
| steps_per_stroke | integer | yes | Plunger increments for a full stroke in the current mode |
| syringe_ul | number | yes | – |
| timestamp | string | yes | – |
| top_speed_flow_ul_s | number | yes | Flow rate the current top speed corresponds to |
| top_speed_pulses_s | integer | yes | – |
| valve_position | string | yes | – |
No examples provided.
initialize Initialize ~149
Initialize the pump: drive the plunger to the top of the syringe (expelling its contents through the valve), set that as position 0 and home the valve. Needed after power-up, a plunger overload or `terminate`. Route the valve output to waste first. Takes a few seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| force | string | – | Plunger force against the syringe top; auto picks it from the syringe size |
| input_port | – | – | Distribution valves: input port |
| output_port | – | – | Distribution valves: output port |
| valve_direction | string | – | Valve homing/port numbering: cw (Z command), ccw (Y), or no_valve (W, plunger only) |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | yes | Meaning of the error code |
| error_code | integer | yes | Error code from the status byte (0 = none) |
| plunger_position_steps | integer | yes | – |
| plunger_position_ul | number | yes | Volume currently drawn into the syringe |
| ready | boolean | yes | True when the pump accepts new move commands (Q status bit 5) |
| resolution_mode | integer | yes | 0 = standard (N0), 1 = fine positioning (N1), 2 = microstep (N2) |
| steps_per_stroke | integer | yes | Plunger increments for a full stroke in the current mode |
| syringe_ul | number | yes | – |
| timestamp | string | yes | – |
| top_speed_flow_ul_s | number | yes | Flow rate the current top speed corresponds to |
| top_speed_pulses_s | integer | yes | – |
| valve_position | string | yes | – |
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_valve Set Valve ~89
Turn the valve to a named position (3/4-port valves) or to a numbered port (distribution valves). In bypass the plunger cannot move. Returns the new status.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Distribution valves: rotation direction to the port |
| port | – | – | Distribution valves: port number |
| position | – | – | Non-distribution valves: input, output, bypass or extra |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | yes | Meaning of the error code |
| error_code | integer | yes | Error code from the status byte (0 = none) |
| plunger_position_steps | integer | yes | – |
| plunger_position_ul | number | yes | Volume currently drawn into the syringe |
| ready | boolean | yes | True when the pump accepts new move commands (Q status bit 5) |
| resolution_mode | integer | yes | 0 = standard (N0), 1 = fine positioning (N1), 2 = microstep (N2) |
| steps_per_stroke | integer | yes | Plunger increments for a full stroke in the current mode |
| syringe_ul | number | yes | – |
| timestamp | string | yes | – |
| top_speed_flow_ul_s | number | yes | Flow rate the current top speed corresponds to |
| top_speed_pulses_s | integer | yes | – |
| valve_position | string | yes | – |
No examples provided.
terminate Terminate ~44
Stop any plunger move, loop or delay immediately (DT command T). A valve move in progress still completes. Re-initialize afterwards: the plunger may have lost steps.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | yes | Meaning of the error code |
| error_code | integer | yes | Error code from the status byte (0 = none) |
| plunger_position_steps | integer | yes | – |
| plunger_position_ul | number | yes | Volume currently drawn into the syringe |
| ready | boolean | yes | True when the pump accepts new move commands (Q status bit 5) |
| resolution_mode | integer | yes | 0 = standard (N0), 1 = fine positioning (N1), 2 = microstep (N2) |
| steps_per_stroke | integer | yes | Plunger increments for a full stroke in the current mode |
| syringe_ul | number | yes | – |
| timestamp | string | yes | – |
| top_speed_flow_ul_s | number | yes | Flow rate the current top speed corresponds to |
| top_speed_pulses_s | integer | yes | – |
| valve_position | string | yes | – |
No examples provided.
How do I install the Tecan Cavro Syringe Pump MCP server?
Tecan Cavro Syringe Pump runs locally as a PyPI package, launched with uvx labmcp-cavro. 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-cavro
claude mcp add k-dense-ai-labmcp-cavro -- uvx labmcp-cavro
What is the Tecan Cavro Syringe Pump MCP server?
Tecan Cavro Syringe Pump is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-cavro. MCP server for Tecan Cavro syringe pumps (XLP 6000, XMP 6000, XCalibur) over the DT protocol. This page covers its PyPI package (labmcp-cavro).
Is the Tecan Cavro Syringe Pump MCP server safe to use?
Tecan Cavro Syringe Pump scores 80 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 Tecan Cavro Syringe Pump MCP server expose?
Tecan Cavro Syringe Pump exposes 9 tools: get_connection_info, get_command_log, reconnect, get_status, initialize, and 4 more. Their descriptions and schemas cost roughly 678 tokens of context every time the server is loaded.
Is the Tecan Cavro Syringe Pump MCP server still maintained?
Tecan Cavro Syringe Pump 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 Tecan Cavro Syringe Pump MCP server under?
Tecan Cavro Syringe Pump 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 Tecan Cavro Syringe Pump MCP server?
VerifyMCP ran 15 checks on Tecan Cavro Syringe Pump, 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 Tecan Cavro Syringe Pump: 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.