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.

EPICS Channel Access

PYPI · LABMCP-EPICS

MCP server for EPICS Channel Access: read, monitor and guarded writes of process variables.

Available components

0 this week 80 Trust /100

Last scanned (15 hours ago)

Scores higher than 78% 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
  • 3 of 19 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 Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1287 tokens (~128/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 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
  • 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 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ 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.

  • 10 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 9 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
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-epics@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-epics-v0.1.2
Rekor log index 2969518482
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:3991a38c7343fa19bfd4a2ec0c48b368e288c56e7630206fab296a6c257bbb20

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 19 packages
Packages resolved 19
Stale 2
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~845 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
apply_safe_state ~68

Emergency action: write the scientist-configured safe-state PVs (--option safe_state, e.g. motor STOP fields, shutter close, HV off), all of them even if one fails. Available in read-only mode. It does not replace the facility's own interlocks and stop buttons.

Input schema present but exposes no named parameters.

NameTypeReqDescription
configuredbooleanyes–
errorsarrayyes–
messagestringyes–
resultsarrayyes–
timestampstringyes–

No examples provided.

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_pv ~96

Read one PV with its metadata: value, units, precision, alarm severity/status, IOC timestamp and age, display/alarm/warning/control limits and enum state names. Waveforms come back downsampled with min/max/mean statistics.

NameTypeReqDescription
max_elementsinteger–Arrays longer than this are downsampled
namestringyesPV name, e.g. 'BL7:MTR1.RBV'
NameTypeReqDescription
age_s–yesSeconds since the IOC timestamp (large = stale value)
alarm_limits––LOLO/HIHI
array_summary–––
as_string––CHAR waveform decoded as a (long) string
control_limits––DRVL/DRVH for output records; writes must lie inside
display_limits–––
downsampledboolean––
element_countintegeryes–
enum_strings–––
namestringyes–
native_typestringyesCA native type: DOUBLE, FLOAT, LONG, INT, CHAR, ENUM or STRING
precision–––
severitystringyesAlarm severity: NO_ALARM, MINOR_ALARM, MAJOR_ALARM or INVALID_ALARM
statusstringyesAlarm status, e.g. NO_ALARM, HIHI, HIGH, LOW, LOLO, UDF, COMM, TIMEOUT
timestamp–yesIOC timestamp of the value (UTC)
units–––
value–yesScalar, string, enum state name, or (possibly downsampled) array
warning_limits––LOW/HIGH

No examples provided.

get_pvs ~75

Read many PVs at once (e.g. all motors or vacuum gauges of a beamline). PVs that cannot be reached are listed in `errors` instead of failing the whole call.

NameTypeReqDescription
max_elementsinteger–Arrays longer than this are downsampled
namesarrayyesPV names
NameTypeReqDescription
errorsarrayyes–
readingsarrayyes–
timestampstringyes–

No examples provided.

monitor_pv ~116

Subscribe to a PV and collect every value change for `duration_s` seconds (or until `max_updates`), then return statistics (min/max/mean/std, drift rate) and the updates.

NameTypeReqDescription
duration_snumber–How long to collect updates
max_pointsinteger–Updates to include in the reply (evenly thinned)
max_updatesinteger–Stop after this many updates
namestringyesPV name, e.g. 'BL7:MTR1.RBV'
NameTypeReqDescription
duration_snumberyes–
n_updatesintegeryes–
namestringyes–
non_finite_updatesinteger–Numeric updates that were NaN or infinite (not in stats)
severities_seenarrayyes–
stats–yesFor numeric PVs (arrays: per-update mean), finite values only
timestampstringyes–
updatesarrayyesUpdates (arrays summarised by their mean), at most max_points

No examples provided.

put_pv ~171

Write a PV. This can move motors, open shutters, change magnet or high-voltage setpoints and heat or cool samples: tell the user exactly what will change first. The write is refused unless the PV matches the put allow-list, the IOC grants write access, and the value has the right type and lies within the PV's control limits (DRVL/DRVH). Returns the read-back value.

NameTypeReqDescription
namestringyesPV name, e.g. 'BL7:MTR1.RBV'
timeout_snumber–Max seconds to wait for completion
value–yesNew value: number, enum state name or index, string, or array for waveforms
waitboolean–Wait for the IOC's put-completion (put-callback)
NameTypeReqDescription
completedbooleanyesTrue if the IOC confirmed completion (put-callback)
elapsed_snumberyes–
namestringyes–
previous_value–yes–
requested–yes–
severitystringyes–
statusstringyes–
timestampstringyes–
value–yesValue read back from the PV after the write
warningsarrayyes–

No examples provided.

put_pvs ~129

Write several PVs in order (e.g. set both slit blades). Every write is validated first (allow- list, access rights, type, control limits); if any is invalid nothing is written. Writing stops at the first failure and the rest are reported as not written. The whole batch must finish within an hour: writes that would start later are not sent.

NameTypeReqDescription
timeout_snumber–Max seconds to wait per write
waitboolean–Wait for each put-completion before the next write
writesarrayyesPV writes, applied in order
NameTypeReqDescription
error–––
not_writtenarrayyesPVs not written because an earlier write failed
resultsarrayyes–
timestampstringyes–

No examples provided.

pv_info ~69

Connection details of a PV: serving IOC host:port, native type, element count, and whether this client has read/write access (EPICS access security) and passes the put allow-list.

NameTypeReqDescription
namestringyesPV name, e.g. 'BL7:MTR1.RBV'
NameTypeReqDescription
connectedbooleanyes–
element_countintegeryes–
namestringyes–
native_typestringyes–
put_allowed_by_allowlistbooleanyes–
read_accessbooleanyes–
serverstringyeshost:port of the IOC (or CA gateway) serving the PV
timestampstringyes–
write_accessbooleanyesEPICS access security grants this client write access

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.

Install

How do I install the EPICS Channel Access MCP server?

EPICS Channel Access runs locally as a PyPI package, launched with uvx labmcp-epics. 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-epics

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

What is the EPICS Channel Access MCP server?

EPICS Channel Access is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-epics. MCP server for EPICS Channel Access: read, monitor and guarded writes of process variables. This page covers its PyPI package (labmcp-epics).

Is the EPICS Channel Access MCP server safe to use?

EPICS Channel Access 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 EPICS Channel Access MCP server expose?

EPICS Channel Access exposes 10 tools: get_connection_info, get_command_log, reconnect, get_pv, get_pvs, and 5 more. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.

Is the EPICS Channel Access MCP server still maintained?

EPICS Channel Access 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 EPICS Channel Access MCP server under?

EPICS Channel Access 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 EPICS Channel Access MCP server?

VerifyMCP ran 15 checks on EPICS Channel Access, 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 EPICS Channel Access: 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.