PalmSens Potentiostat
PYPI · LABMCP-PALMSENS
MCP server for PalmSens potentiostats running MethodSCRIPT (EmStat Pico, EmStat4, Sensit, Nexus).
Available components
Last scanned (14 hours ago)
Scores higher than 96% 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 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1743 tokens (~174/item across 10 items; 10 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% 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
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 →
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 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Nov 26 0
- Stability: 0.97 → pass security
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-palmsens@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-palmsens-v0.1.3 |
| Rekor log index | 2969517767 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:826c4f3c35e9c9917469fb42a3570a3a3dbb5f7d93782fd71d98470210acfe28 |
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 →
abort_measurement Abort Measurement ~39
Abort the running measurement or script immediately (communication command Z) and make sure the cell is switched off. Safe to call when nothing is running.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
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_device_info Get Device Info ~43
Identify the potentiostat (model, firmware, serial number) and list its potential window, PGStat modes and current ranges, so measurement parameters can be chosen within them.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
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.
run_chronoamperometry Run Chronoamperometry ~202
Hold the cell at `potential_v` for `run_time_s` and record the current every `interval_s`. Returns the data (time from the instrument timer) plus first/last/mean current and the charge. Applies potential to the cell.
| Name | Type | Req | Description |
|---|---|---|---|
| autorange | boolean | – | Let the instrument switch to lower current ranges automatically |
| current_range_a | number | – | Highest expected |current| in A; sets the (maximum) current range |
| equilibration_s | number | – | Seconds to hold the begin potential before the technique starts |
| interval_s | number | – | Time between points, s |
| max_points | integer | – | Maximum number of points to return |
| potential_v | number | yes | Applied DC potential, V vs RE |
| run_time_s | number | yes | Total measurement time, s |
| save_path | – | – | Write every point to this new .csv file (optional; never overwrites a file) |
| Name | Type | Req | Description |
|---|---|---|---|
| aborted | boolean | yes | True if the measurement was aborted before completion |
| cv_peaks | – | – | Per-scan peaks (CV only; raw extrema, no baseline) |
| data | array | yes | Downsampled data (every n-th point, including the last) |
| device | string | yes | – |
| duration_s | number | yes | – |
| n_points | integer | yes | Number of points measured |
| parameters | object | yes | Technique parameters as sent to the instrument |
| returned_points | integer | yes | – |
| saved_path | – | – | – |
| simulated | boolean | yes | True if this data came from the built-in simulator |
| started_at | string | yes | – |
| summary | object | yes | Summary statistics computed from all points |
| technique | string | yes | – |
| timestamp | string | yes | – |
| warnings | array | yes | – |
No examples provided.
run_cyclic_voltammetry Run Cyclic Voltammetry ~270
Run a cyclic voltammogram: begin -> vertex 1 -> vertex 2 -> begin, `n_scans` times, and return potential/current/time data with the anodic and cathodic peaks of every scan. Applies potential to the cell for the whole scan; the cell is switched off at the end.
| Name | Type | Req | Description |
|---|---|---|---|
| autorange | boolean | – | Let the instrument switch to lower current ranges automatically |
| begin_potential_v | number | yes | Start (and end) potential, V vs RE |
| current_range_a | number | – | Highest expected |current| in A; sets the (maximum) current range |
| equilibration_s | number | – | Seconds to hold the begin potential before the technique starts |
| max_points | integer | – | Maximum number of points to return |
| n_scans | integer | – | Number of cycles |
| save_path | – | – | Write every point to this new .csv file (optional; never overwrites a file) |
| scan_rate_v_s | number | – | Scan rate, V/s |
| step_potential_v | number | – | Potential step, V |
| vertex1_potential_v | number | yes | First vertex, V vs RE |
| vertex2_potential_v | number | yes | Second vertex, V vs RE |
| Name | Type | Req | Description |
|---|---|---|---|
| aborted | boolean | yes | True if the measurement was aborted before completion |
| cv_peaks | – | – | Per-scan peaks (CV only; raw extrema, no baseline) |
| data | array | yes | Downsampled data (every n-th point, including the last) |
| device | string | yes | – |
| duration_s | number | yes | – |
| n_points | integer | yes | Number of points measured |
| parameters | object | yes | Technique parameters as sent to the instrument |
| returned_points | integer | yes | – |
| saved_path | – | – | – |
| simulated | boolean | yes | True if this data came from the built-in simulator |
| started_at | string | yes | – |
| summary | object | yes | Summary statistics computed from all points |
| technique | string | yes | – |
| timestamp | string | yes | – |
| warnings | array | yes | – |
No examples provided.
run_differential_pulse_voltammetry Run Differential Pulse Voltammetry ~257
Run differential pulse voltammetry (current = forward - reverse, per step) from begin to end potential and return the data with the peak current and peak potential. The scan rate must be below step / pulse_time / 2. Applies potential to the cell.
| Name | Type | Req | Description |
|---|---|---|---|
| autorange | boolean | – | Let the instrument switch to lower current ranges automatically |
| begin_potential_v | number | yes | Start potential, V vs RE |
| current_range_a | number | – | Highest expected |current| in A; sets the (maximum) current range |
| end_potential_v | number | yes | End potential, V vs RE |
| equilibration_s | number | – | Seconds to hold the begin potential before the technique starts |
| max_points | integer | – | Maximum number of points to return |
| pulse_potential_v | number | – | Pulse amplitude, V (absolute) |
| pulse_time_s | number | – | Pulse duration, s |
| save_path | – | – | Write every point to this new .csv file (optional; never overwrites a file) |
| scan_rate_v_s | number | – | Scan rate, V/s |
| step_potential_v | number | – | Potential step, V |
| Name | Type | Req | Description |
|---|---|---|---|
| aborted | boolean | yes | True if the measurement was aborted before completion |
| cv_peaks | – | – | Per-scan peaks (CV only; raw extrema, no baseline) |
| data | array | yes | Downsampled data (every n-th point, including the last) |
| device | string | yes | – |
| duration_s | number | yes | – |
| n_points | integer | yes | Number of points measured |
| parameters | object | yes | Technique parameters as sent to the instrument |
| returned_points | integer | yes | – |
| saved_path | – | – | – |
| simulated | boolean | yes | True if this data came from the built-in simulator |
| started_at | string | yes | – |
| summary | object | yes | Summary statistics computed from all points |
| technique | string | yes | – |
| timestamp | string | yes | – |
| warnings | array | yes | – |
No examples provided.
run_linear_sweep_voltammetry Run Linear Sweep Voltammetry ~215
Run a linear sweep voltammogram from `begin_potential_v` to `end_potential_v` and return the data with the largest/smallest current and where they occur. Applies potential to the cell.
| Name | Type | Req | Description |
|---|---|---|---|
| autorange | boolean | – | Let the instrument switch to lower current ranges automatically |
| begin_potential_v | number | yes | Start potential, V vs RE |
| current_range_a | number | – | Highest expected |current| in A; sets the (maximum) current range |
| end_potential_v | number | yes | End potential, V vs RE |
| equilibration_s | number | – | Seconds to hold the begin potential before the technique starts |
| max_points | integer | – | Maximum number of points to return |
| save_path | – | – | Write every point to this new .csv file (optional; never overwrites a file) |
| scan_rate_v_s | number | – | Scan rate, V/s |
| step_potential_v | number | – | Potential step, V |
| Name | Type | Req | Description |
|---|---|---|---|
| aborted | boolean | yes | True if the measurement was aborted before completion |
| cv_peaks | – | – | Per-scan peaks (CV only; raw extrema, no baseline) |
| data | array | yes | Downsampled data (every n-th point, including the last) |
| device | string | yes | – |
| duration_s | number | yes | – |
| n_points | integer | yes | Number of points measured |
| parameters | object | yes | Technique parameters as sent to the instrument |
| returned_points | integer | yes | – |
| saved_path | – | – | – |
| simulated | boolean | yes | True if this data came from the built-in simulator |
| started_at | string | yes | – |
| summary | object | yes | Summary statistics computed from all points |
| technique | string | yes | – |
| timestamp | string | yes | – |
| warnings | array | yes | – |
No examples provided.
run_methodscript Run Methodscript ~217
Advanced: run a raw MethodSCRIPT and return its raw output and decoded data packages. Literal potentials of set_e / set_range_minmax da and the CV, LSV, DPV, SWV, NPV, ACV, CA, PAD, EIS and fast CV/CA techniques are checked against `max_potential_v`, and literal `set_range ba` / `set_autoranging ba` currents against `max_current_range_a`; values computed at run time are not. Aborted after `timeout_s`; add `on_finished:` + `cell_off` to your script so the cell is switched off after an abort. After a runtime error, a timeout or `abort_measurement` the server switches the cell off itself.
| Name | Type | Req | Description |
|---|---|---|---|
| max_lines | integer | – | Maximum output lines/packages to return |
| script | string | yes | MethodSCRIPT, one command per line (a leading 'e' line is ignored) |
| timeout_s | number | – | Abort the script after this |
| Name | Type | Req | Description |
|---|---|---|---|
| aborted | boolean | yes | – |
| cell_off_after_error | – | – | After a runtime error (on_finished: is skipped) or a timeout: True if the server's cell_off script succeeded, False if it failed (the cell may still be on) |
| duration_s | number | yes | – |
| error | – | yes | – |
| output_lines | array | yes | Raw output lines (truncated to max_lines) |
| packages | array | yes | Data packages as {VarType: value} (None for 'nan'), truncated to max_lines |
| simulated | boolean | yes | – |
| texts | array | yes | send_string output |
| timed_out | boolean | yes | – |
| timestamp | string | yes | – |
| total_lines | integer | yes | – |
| total_packages | integer | yes | – |
No examples provided.
How do I install the PalmSens Potentiostat MCP server?
PalmSens Potentiostat runs locally as a PyPI package, launched with uvx labmcp-palmsens. 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-palmsens
claude mcp add k-dense-ai-labmcp-palmsens -- uvx labmcp-palmsens
What is the PalmSens Potentiostat MCP server?
PalmSens Potentiostat is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-palmsens. MCP server for PalmSens potentiostats running MethodSCRIPT (EmStat Pico, EmStat4, Sensit, Nexus). This page covers its PyPI package (labmcp-palmsens).
Is the PalmSens Potentiostat MCP server safe to use?
PalmSens Potentiostat scores 94 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 PalmSens Potentiostat MCP server expose?
PalmSens Potentiostat exposes 10 tools: get_connection_info, get_command_log, reconnect, get_device_info, run_cyclic_voltammetry, and 5 more. Their descriptions and schemas cost roughly 1,364 tokens of context every time the server is loaded.
Is the PalmSens Potentiostat MCP server still maintained?
PalmSens Potentiostat 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 PalmSens Potentiostat MCP server under?
PalmSens Potentiostat 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 PalmSens Potentiostat MCP server?
VerifyMCP ran 16 checks on PalmSens Potentiostat, 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.