Atlas Scientific EZO Sensors
PYPI · LABMCP-ATLAS-EZO · SCANNED SEP 30
MCP server for Atlas Scientific EZO sensor circuits (pH, ORP, DO, EC, RTD, HUM, CO2, PRS) over UART.
Available components
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 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1426 tokens (~109/item across 13 items; 13 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% 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 14 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
How do I install the Atlas Scientific EZO Sensors MCP server?
Atlas Scientific EZO Sensors runs locally as a PyPI package, launched with uvx labmcp-atlas-ezo. 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-atlas-ezo
claude mcp add k-dense-ai-labmcp-atlas-ezo -- uvx labmcp-atlas-ezo
{
"mcpServers": {
"k-dense-ai-labmcp-atlas-ezo": {
"command": "uvx",
"args": [
"labmcp-atlas-ezo"
]
}
}
} {
"servers": {
"k-dense-ai-labmcp-atlas-ezo": {
"command": "uvx",
"args": [
"labmcp-atlas-ezo"
]
}
}
} codex mcp add k-dense-ai-labmcp-atlas-ezo -- uvx labmcp-atlas-ezo
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"k-dense-ai-labmcp-atlas-ezo": {
"type": "local",
"command": [
"uvx",
"labmcp-atlas-ezo"
],
"enabled": true
}
}
} openclaw mcp add k-dense-ai-labmcp-atlas-ezo --command uvx --arg labmcp-atlas-ezo
mcp_servers:
k-dense-ai-labmcp-atlas-ezo:
command: "uvx"
args: ["labmcp-atlas-ezo"] {
"McpServers": {
"k-dense-ai-labmcp-atlas-ezo": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"labmcp-atlas-ezo"
]
}
}
} assistant mcp add k-dense-ai-labmcp-atlas-ezo -t stdio -c uvx -a labmcp-atlas-ezo
{
"mcpServers": {
"k-dense-ai-labmcp-atlas-ezo": {
"command": "uvx",
"args": [
"labmcp-atlas-ezo"
]
}
}
} 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.
- 29 Sept 26 +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.
- 28 Sept 26 +29
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −33
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.2 functional
- 26 Sept 26 0
- Tool safety: pass → unverified ▼ security
- Malware scan: 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.0 → 0.1.1 functional
- 25 Sept 26 72
First indexed and scored.
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 30 Sept 2026 · Analysed pypi/labmcp-atlas-ezo@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-atlas-ezo-v0.1.2 |
| Rekor log index | 2969516803 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3dbeb30677041b1cf21b711d21f6f83055e90aaee570a4f3eb7588ff78d50a46 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | 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 →
calibrate Calibrate ~187
Store one calibration point. The probe must already be in the named standard (buffer, air, dry, ...) with a stable reading. Point names are validated per circuit type. pH: a `mid` calibration erases existing low/high points, so always do mid first. EC: do `dry` first.
| Name | Type | Req | Description |
|---|---|---|---|
| point | string | yes | pH: mid|low|high; ORP: single; DO: atmospheric|zero; EC: dry|single|low|high; RTD: single; CO2: zero|high; PRS: zero|high |
| value | – | – | Value of the standard the probe is in (pH units, mV, µS/cm, temperature in the RTD's current scale, ppm CO2, pressure in current units). Omit for DO atmospheric/zero, EC dry and CO2/PRS zero. |
| Name | Type | Req | Description |
|---|---|---|---|
| calibration_points | integer | yes | – |
| meaning | string | yes | – |
| message | string | yes | – |
| point | string | yes | – |
| reference_value | – | yes | – |
No examples provided.
clear_calibration Clear Calibration ~57
Delete all stored calibration data (Cal,clear). pH/ORP/DO/EC/RTD return to uncalibrated; CO2/PRS return to their factory calibration. The probe must be recalibrated afterwards.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| advice | string | yes | – |
| meaning | string | yes | – |
| ph_acid_slope_percent | – | – | pH only: acid slope vs ideal probe (%) |
| ph_base_slope_percent | – | – | pH only: base slope vs ideal probe (%) |
| ph_zero_offset_mv | – | – | pH only: zero-point offset (mV) |
| points | integer | yes | – |
| sensor | string | yes | – |
| valid_points | array | yes | – |
No examples provided.
get_calibration_status Get Calibration Status ~46
Report how many calibration points are stored and what that means for this circuit type; for pH also the probe slope (acid/base % of ideal and zero offset in mV).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| advice | string | yes | – |
| meaning | string | yes | – |
| ph_acid_slope_percent | – | – | pH only: acid slope vs ideal probe (%) |
| ph_base_slope_percent | – | – | pH only: base slope vs ideal probe (%) |
| ph_zero_offset_mv | – | – | pH only: zero-point offset (mV) |
| points | integer | yes | – |
| sensor | string | yes | – |
| valid_points | array | 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_info Get Info ~54
Report the circuit type, firmware, device name, supply voltage and last restart reason, LED state, calibration state, temperature compensation and type-specific settings (enabled outputs, EC probe constant K, DO salinity/pressure compensation).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| calibration | – | yes | – |
| calibration_point_names | array | yes | – |
| calibration_points | – | yes | – |
| device_name | – | yes | – |
| do_pressure_kpa | – | – | DO atmospheric pressure compensation |
| do_salinity | – | – | DO salinity compensation |
| enabled_outputs | array | yes | – |
| firmware | string | yes | – |
| led_on | – | yes | – |
| model | string | yes | – |
| notes | array | yes | – |
| probe_constant_k | – | – | EC probe cell constant K |
| restart_reason | – | yes | – |
| sensor | string | yes | – |
| supply_voltage_v | – | yes | – |
| temperature_compensation_c | – | yes | – |
No examples provided.
log_series Log Series ~107
Record a series of readings (e.g. to watch a probe stabilise before calibrating, follow pH or DO in a bioreactor, or log temperature). Returns every point plus mean, stdev, min, max and drift per minute for each output.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of readings |
| interval_s | number | – | Seconds between readings (>= 1) |
| save_path | – | – | Optional new .csv file for the full series (never overwritten) |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| points | array | yes | – |
| saved_to | – | – | – |
| sensor | string | yes | – |
| stats | array | yes | – |
No examples provided.
read_value Read Value ~91
Take one reading (about 1 s) and return every enabled output with its unit: pH; ORP in mV; DO in mg/L (and % saturation if enabled); EC in µS/cm plus TDS (ppm), salinity (PSU) and specific gravity if enabled; RTD temperature; humidity %RH (+ air temperature, dew point); CO2 ppm; or pressure.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| raw | string | yes | – |
| sensor | string | yes | Circuit type, e.g. 'pH', 'Dissolved oxygen' |
| temperature_compensation_c | – | – | Temperature the reading is compensated to (pH, EC, DO only) |
| timestamp | string | yes | UTC time of the reading (ISO 8601) |
| unit | string | yes | Unit of the primary output |
| value | number | yes | The primary output (first value) |
| values | array | yes | Every enabled output of the circuit |
| warnings | array | – | – |
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_do_compensation Set Do Compensation ~107
DO circuits only: set salinity compensation (irrelevant below ~2500 µS/cm) and/or atmospheric pressure compensation (default 101.3 kPa; lower at altitude). Neither is retained through a power cycle.
| Name | Type | Req | Description |
|---|---|---|---|
| pressure_kpa | – | – | Atmospheric pressure in kPa |
| salinity | – | – | Sample salinity (see salinity_unit) |
| salinity_unit | string | – | 'us_cm' (µS/cm) or 'ppt' |
| Name | Type | Req | Description |
|---|---|---|---|
| calibration | – | yes | – |
| calibration_point_names | array | yes | – |
| calibration_points | – | yes | – |
| device_name | – | yes | – |
| do_pressure_kpa | – | – | DO atmospheric pressure compensation |
| do_salinity | – | – | DO salinity compensation |
| enabled_outputs | array | yes | – |
| firmware | string | yes | – |
| led_on | – | yes | – |
| model | string | yes | – |
| notes | array | yes | – |
| probe_constant_k | – | – | EC probe cell constant K |
| restart_reason | – | yes | – |
| sensor | string | yes | – |
| supply_voltage_v | – | yes | – |
| temperature_compensation_c | – | yes | – |
No examples provided.
set_led Set Led ~48
Turn the circuit's status LED on or off. Returns the new LED state.
| Name | Type | Req | Description |
|---|---|---|---|
| on | boolean | yes | True = LED on (default), False = off (e.g. light-sensitive cultures) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | boolean | yes | – |
No examples provided.
set_probe_constant Set Probe Constant ~75
EC circuits only: set the conductivity probe's cell constant K to match the probe (printed on it). Recalibrate after changing it. Returns the K now in use.
| Name | Type | Req | Description |
|---|---|---|---|
| k | number | yes | Cell constant K of the EC probe (e.g. 0.1, 1.0, 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | number | yes | – |
No examples provided.
set_temperature_compensation Set Temperature Compensation ~60
Set the sample temperature used to compensate pH, EC or DO readings (T,n; always °C). Not retained through a power cycle. Returns the value the circuit now uses.
| Name | Type | Req | Description |
|---|---|---|---|
| temperature_c | number | yes | Sample temperature in °C |
| Name | Type | Req | Description |
|---|---|---|---|
| result | number | yes | – |
No examples provided.
What is the Atlas Scientific EZO Sensors MCP server?
Atlas Scientific EZO Sensors is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-atlas-ezo. MCP server for Atlas Scientific EZO sensor circuits (pH, ORP, DO, EC, RTD, HUM, CO2, PRS) over UART. This page covers its PyPI package (labmcp-atlas-ezo).
Is the Atlas Scientific EZO Sensors MCP server safe to use?
Atlas Scientific EZO Sensors scores 69 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 Atlas Scientific EZO Sensors MCP server expose?
Atlas Scientific EZO Sensors exposes 13 tools: get_connection_info, get_command_log, reconnect, read_value, get_info, and 8 more. Their descriptions and schemas cost roughly 953 tokens of context every time the server is loaded.
Is the Atlas Scientific EZO Sensors MCP server still maintained?
Atlas Scientific EZO Sensors 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 Atlas Scientific EZO Sensors MCP server under?
Atlas Scientific EZO Sensors 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.