EPICS Channel Access runs on your own machine — the client starts it, so there is no endpoint to ping. 205 installs a week from pypi. Last commit 27 Sep 2026.
MCP server for EPICS Channel Access: read, monitor and guarded writes of process variables.
We read the source, 6 d ago · rules ccca72095570
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
subprocess.run( # noqa: S603, S607
data = yaml.load(text, Loader=_strict_yaml_loader()) # noqa: S506 - a SafeLoader subclass
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check EPICS Channel Access every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add labmcp-epics -- uvx labmcp-epics
{
"mcpServers": {
"labmcp-epics": {
"args": [
"labmcp-epics"
],
"command": "uvx"
}
}
}
[mcp_servers.labmcp-epics]
command = "uvx"
args = ["labmcp-epics"]
{
"mcpServers": {
"labmcp-epics": {
"args": [
"labmcp-epics"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"labmcp-epics": {
"args": [
"labmcp-epics"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
LABMCP_ADDRESS (Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025), LABMCP_SIMULATE (Set to 1 to use the built-in simulator (no hardware)), LABMCP_READ_ONLY (Set to 1 to disable all state-changing tools), LABMCP_LIMITS (Safety limit overrides, e.g. max_temperature_c=80).
The author declared them in the registry entry; get the values from the project itself.
MCP server for Hatchbox Rails hosting — env var inspection, deploys, and process monitoring.
MCP server for Site Spy — lets AI agents monitor websites for changes
Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.
MCP server for ChangeDetection.io website monitoring and change history.
Remote MCP server for hotel rate monitoring, parity checks, and pricing intelligence via Apify.
Stdio MCP server for PromptEden projects, monitors, answers, and analytics.
Create, read and monitor Wachete website-change wachets for a signed-in user.
MCP server for Duplicacy — monitor backup status and Prometheus metrics
Answers built from our own checks of this server.