# PalmSens Potentiostat (pypi · labmcp-palmsens)

MCP server for PalmSens potentiostats running MethodSCRIPT (EmStat Pico, EmStat4, Sensit, Nexus).

- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- pypi · `labmcp-palmsens`: 82/100 (this document), [markdown](https://verifymcp.io/servers/k-dense-ai-labmcp-palmsens/labmcp-palmsens.md), [page](https://verifymcp.io/servers/k-dense-ai-labmcp-palmsens/labmcp-palmsens)

## Channel facts

- Registry: `pypi`
- Package: `labmcp-palmsens`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-30.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 2 of 17 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to K-Dense-AI/lab-instrument-mcps).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add k-dense-ai-labmcp-palmsens -- uvx labmcp-palmsens
```

### Cursor

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-palmsens": {
      "command": "uvx",
      "args": [
        "labmcp-palmsens"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k-dense-ai-labmcp-palmsens": {
      "command": "uvx",
      "args": [
        "labmcp-palmsens"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add k-dense-ai-labmcp-palmsens -- uvx labmcp-palmsens
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-dense-ai-labmcp-palmsens": {
      "type": "local",
      "command": [
        "uvx",
        "labmcp-palmsens"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k-dense-ai-labmcp-palmsens --command uvx --arg labmcp-palmsens
```

### Hermes

```yaml
mcp_servers:
  k-dense-ai-labmcp-palmsens:
    command: "uvx"
    args: ["labmcp-palmsens"]
```

### Netclaw

```json
{
  "McpServers": {
    "k-dense-ai-labmcp-palmsens": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "labmcp-palmsens"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add k-dense-ai-labmcp-palmsens -t stdio -c uvx -a labmcp-palmsens
```

### Other

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-palmsens": {
      "command": "uvx",
      "args": [
        "labmcp-palmsens"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-30 (score 82, +1)

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

### 2026-09-28 (score 81, +42)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 39, −31)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.2 → 0.1.3

### 2026-09-26 (score 70)

First indexed and scored.

## MCP tools (10)

### `get_connection_info` (~40 tokens)

Get Connection Info

Report which instrument is connected (identity, address, simulated or real),
whether the server is read-only, and the active safety limits. Call this first.

### `get_command_log` (~46 tokens)

Get Command Log

Return the most recent raw commands sent to / replies received from the
instrument (newest last). Useful for debugging and for recording what was done.

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (array)

### `reconnect` (~35 tokens)

Reconnect

Close and re-open the connection to the instrument (e.g. after it was power
cycled or a cable was re-plugged).

### `get_device_info` (~43 tokens)

Get Device Info

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.

### `run_cyclic_voltammetry` (~270 tokens)

Run Cyclic Voltammetry

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.

Input parameters:

- `autorange` (boolean): Let the instrument switch to lower current ranges automatically
- `begin_potential_v` (number, required): 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, required): First vertex, V vs RE
- `vertex2_potential_v` (number, required): Second vertex, V vs RE

Output parameters:

- `aborted` (boolean): True if the measurement was aborted before completion
- `cv_peaks`: Per-scan peaks (CV only; raw extrema, no baseline)
- `data` (array): Downsampled data (every n-th point, including the last)
- `device` (string)
- `duration_s` (number)
- `n_points` (integer): Number of points measured
- `parameters` (object): Technique parameters as sent to the instrument
- `returned_points` (integer)
- `saved_path`
- `simulated` (boolean): True if this data came from the built-in simulator
- `started_at` (string)
- `summary` (object): Summary statistics computed from all points
- `technique` (string)
- `timestamp` (string)
- `warnings` (array)

### `run_linear_sweep_voltammetry` (~215 tokens)

Run Linear Sweep Voltammetry

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.

Input parameters:

- `autorange` (boolean): Let the instrument switch to lower current ranges automatically
- `begin_potential_v` (number, required): Start potential, V vs RE
- `current_range_a` (number): Highest expected |current| in A; sets the (maximum) current range
- `end_potential_v` (number, required): 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

Output parameters:

- `aborted` (boolean): True if the measurement was aborted before completion
- `cv_peaks`: Per-scan peaks (CV only; raw extrema, no baseline)
- `data` (array): Downsampled data (every n-th point, including the last)
- `device` (string)
- `duration_s` (number)
- `n_points` (integer): Number of points measured
- `parameters` (object): Technique parameters as sent to the instrument
- `returned_points` (integer)
- `saved_path`
- `simulated` (boolean): True if this data came from the built-in simulator
- `started_at` (string)
- `summary` (object): Summary statistics computed from all points
- `technique` (string)
- `timestamp` (string)
- `warnings` (array)

### `run_differential_pulse_voltammetry` (~257 tokens)

Run Differential Pulse Voltammetry

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.

Input parameters:

- `autorange` (boolean): Let the instrument switch to lower current ranges automatically
- `begin_potential_v` (number, required): Start potential, V vs RE
- `current_range_a` (number): Highest expected |current| in A; sets the (maximum) current range
- `end_potential_v` (number, required): 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

Output parameters:

- `aborted` (boolean): True if the measurement was aborted before completion
- `cv_peaks`: Per-scan peaks (CV only; raw extrema, no baseline)
- `data` (array): Downsampled data (every n-th point, including the last)
- `device` (string)
- `duration_s` (number)
- `n_points` (integer): Number of points measured
- `parameters` (object): Technique parameters as sent to the instrument
- `returned_points` (integer)
- `saved_path`
- `simulated` (boolean): True if this data came from the built-in simulator
- `started_at` (string)
- `summary` (object): Summary statistics computed from all points
- `technique` (string)
- `timestamp` (string)
- `warnings` (array)

### `run_chronoamperometry` (~202 tokens)

Run Chronoamperometry

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.

Input parameters:

- `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, required): Applied DC potential, V vs RE
- `run_time_s` (number, required): Total measurement time, s
- `save_path`: Write every point to this new .csv file (optional; never overwrites a file)

Output parameters:

- `aborted` (boolean): True if the measurement was aborted before completion
- `cv_peaks`: Per-scan peaks (CV only; raw extrema, no baseline)
- `data` (array): Downsampled data (every n-th point, including the last)
- `device` (string)
- `duration_s` (number)
- `n_points` (integer): Number of points measured
- `parameters` (object): Technique parameters as sent to the instrument
- `returned_points` (integer)
- `saved_path`
- `simulated` (boolean): True if this data came from the built-in simulator
- `started_at` (string)
- `summary` (object): Summary statistics computed from all points
- `technique` (string)
- `timestamp` (string)
- `warnings` (array)

### `run_methodscript` (~217 tokens)

Run Methodscript

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.

Input parameters:

- `max_lines` (integer): Maximum output lines/packages to return
- `script` (string, required): MethodSCRIPT, one command per line (a leading 'e' line is ignored)
- `timeout_s` (number): Abort the script after this

Output parameters:

- `aborted` (boolean)
- `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)
- `error`
- `output_lines` (array): Raw output lines (truncated to max_lines)
- `packages` (array): Data packages as {VarType: value} (None for 'nan'), truncated to max_lines
- `simulated` (boolean)
- `texts` (array): send_string output
- `timed_out` (boolean)
- `timestamp` (string)
- `total_lines` (integer)
- `total_packages` (integer)

### `abort_measurement` (~39 tokens)

Abort Measurement

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.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/k-dense-ai-labmcp-palmsens/labmcp-palmsens#diagnostics

## Score history

- 2026-09-30: 82
- 2026-09-29: 81
- 2026-09-28: 81
- 2026-09-27: 39
- 2026-09-26: 70

## Common questions

### 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 82 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 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 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 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.

## Links

- PyPI project: https://pypi.org/project/labmcp-palmsens/
- Socket report: https://socket.dev/pypi/package/labmcp-palmsens
- Repository: https://github.com/K-Dense-AI/lab-instrument-mcps
- Website: https://github.com/K-Dense-AI/lab-instrument-mcps/tree/main/servers/chemistry/palmsens-potentiostat
- Changelog RSS feed: https://verifymcp.io/servers/k-dense-ai-labmcp-palmsens/labmcp-palmsens.xml
- Changelog JSON feed: https://verifymcp.io/servers/k-dense-ai-labmcp-palmsens/labmcp-palmsens.json
- HTML version of this page: https://verifymcp.io/servers/k-dense-ai-labmcp-palmsens/labmcp-palmsens