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.

io.github.ctrlpi/ctrlpi-mcp

NPM · CTRLPI-MCP

MCP server to control Raspberry Pi, Pico W and ESP32 GPIO agents from an AI assistant.

Available components

68 Trust /100

Last scanned (17 hours ago)

Scores higher than 39% of npm servers

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1878 tokens (~104/item across 18 items; 18 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

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 +1

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

  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 +1
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.9.40 → 0.9.41 functional
  • 17 Nov 26 51

    First indexed and scored.

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 npm/ctrlpi-mcp@0.9.41

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~1,878 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
mcp_agent_logs ~33

Read the last 50 lines of `agent`'s server log file.

NameTypeReqDescription
agentstringyes–

No output schema declared.

No examples provided.

mcp_agent_restart ~65

Restart `agent`'s server process. Pass reboot=true to reboot the whole device instead (a Pi, Pico or ESP32); an agent running on a Mac ignores it and restarts the process.

NameTypeReqDescription
agentstringyes–
rebootboolean––

No output schema declared.

No examples provided.

mcp_agent_upgrade ~70

Upgrade `agent` to the latest release, then restart it. A Pi runs `install.sh --upgrade` (re-downloads the release files and reinstalls dependencies); a Pico or ESP32 downloads the new files over WiFi, swaps them in and resets.

NameTypeReqDescription
agentstringyes–

No output schema declared.

No examples provided.

mcp_agents_list ~161

List configured agents (Pi, Pico or ESP32). Returns name, ip, port, online (live /hello probe), type (pi/pico/esp32), version, has_default_key, and last_updated_at (UTC "YYYY-MM-DD HH:MM:SS", when the agent list was last saved; every sweep saves it). Unreachable agents are included (online=false). The LAN is swept automatically every hour. Pass rescan=true to sweep it now, but only when the user asks to find new hardware: a sweep takes 10 seconds or more. If has_default_key is true for any agent, tell the user that agent is on the insecure default key and ask whether to change it.

NameTypeReqDescription
rescanboolean––

No output schema declared.

No examples provided.

mcp_config_load ~61

Load a full config onto `agent` from a dict (the agent saves a backup first). Pass an empty dict {} to reset all settings on the agent keeping only its API key.

NameTypeReqDescription
agentstringyes–
configobjectyes–

No output schema declared.

No examples provided.

mcp_config_read ~107

Read `agent`'s global application configuration, grouped: `notifications` (`webhook` + `webhook_key`), `bridges` (matter/homekit/homebridge callbacks), `settings` (docs_enabled, logs_enabled, log_days), `sensors`, and configured pins (`gpios`). The `agent` block (platform, os, ip, cpu_temperature, version) is computed live on every read and is not stored.

NameTypeReqDescription
agentstringyes–

No output schema declared.

No examples provided.

mcp_config_write ~196

Update `agent`'s global configuration dynamically. These are the ungrouped (root) field names; the agent routes each into its group (webhook_url -> notifications.webhook, webhook_key -> notifications.webhook_key, docs_enabled/logs_enabled/log_days -> settings), so a read afterwards shows them nested. log_days controls how long log entries are kept (0-30, clamped; 0 clears the log immediately and keeps only the last hour). docs_enabled is Pi-only. Changing api_key changes the agent's authentication key immediately, and also updates the local agents-config.json file to match automatically.

NameTypeReqDescription
agentstringyes–
api_keystring––
docs_enabledboolean––
log_daysnumber––
logs_enabledboolean––
namestring––
webhook_keystring––
webhook_urlstring––

No output schema declared.

No examples provided.

mcp_gpio_config ~156

Configure a GPIO pin on `agent` by number. type: input/output/vcc/gnd/remove. init: 0/1/last. pullup: up/down/none (input only). max: max pulse duration in seconds (output only). reversed: active-low logic (input/output only). watched: trigger webhook on state change (logged on the agent if no notifications.webhook is configured).

NameTypeReqDescription
agentstringyes–
gpiostringyes–
initstring––
maxnumber––
namestring––
pullupstring––
reversedboolean––
typestring––
watchedboolean––

No output schema declared.

No examples provided.

mcp_gpio_read ~49

Read a GPIO pin value on `agent` by number or name, or 'all' to read all pins.

NameTypeReqDescription
agentstringyes–
name_or_gpiostringyes–

No output schema declared.

No examples provided.

mcp_gpio_scan ~122

Scan all hardware GPIO pins on `agent` and return each pin's level (the physical state), type, pull resistor and name; a reversed pin also reports `value` (its logical state) and `reversed`. Pins: BCM 2-27 on a Raspberry Pi, GP0-GP28 (minus the WiFi-reserved GP23/24/25/29) on a Pico, and every usable pin of the chip on an ESP32 (flash, PSRAM and USB pins are left out).

NameTypeReqDescription
agentstringyes–

No output schema declared.

No examples provided.

mcp_gpio_watched ~37

List the GPIO pins that are currently being actively watched (the ones emitting hardware interrupts/webhooks).

NameTypeReqDescription
agentstringyes–

No output schema declared.

No examples provided.

mcp_gpio_write ~127

Write a value to a GPIO pin on `agent` ('0', '1', 'on', 'off', or 'toggle'). Optional duration in seconds, after which the pin reverts to its previous state. If the pin has a configured 'max' pulse duration, the effective duration is clamped to it - and if no duration is given but 'max' is set, 'max' is used as the duration automatically.

NameTypeReqDescription
agentstringyes–
durationnumber––
name_or_gpiostringyes–
valuestringyes–

No output schema declared.

No examples provided.

mcp_script_list ~89

List the files in `agent`'s scripts/ folder (the folder sensors run from): `scripts` ([{name, size, modified}]) and `write`: "enabled", "default_key" (writes are refused until the agent's api_key is changed from the default) or "locked" (a write.lock file there blocks every write).

NameTypeReqDescription
agentstringyes–

No output schema declared.

No examples provided.

mcp_script_read ~43

Read one file from `agent`'s scripts/ folder. Returns {name, content}.

NameTypeReqDescription
agentstringyes–
namestringyes–

No output schema declared.

No examples provided.

mcp_script_run ~141

Run a file from `agent`'s scripts/ folder and return {name, exit_code, output}. On a Raspberry Pi a .py runs with the agent's Python and anything else with `sh`; output is its stdout (first 2 KB) and a run over 15 s is killed. On a Pico or ESP32 the file is exec'd in-process: output is what its read(*args) returns, or its `result`, and exit_code is 1 if it raised. `args` are letters and digits only.

NameTypeReqDescription
agentstringyes–
argsarray––
namestringyes–

No output schema declared.

No examples provided.

mcp_script_write ~179

Create or overwrite a file in `agent`'s scripts/ folder with `content`, or delete it with remove=true. `name` is a bare filename of up to 32 characters (letters, digits, . _ -, no leading dot or dash, no paths). Refused while the agent still has the default api_key, and once a write.lock file is in the folder. Writing write.lock (any content) locks every script write, and this tool can then no longer change or remove it. The lock does not stop runs: a script run with mcp_script_run that deletes files can remove write.lock, as can a shell (Pi) or USB (Pico, ESP32).

NameTypeReqDescription
agentstringyes–
contentstring––
namestringyes–
removeboolean––

No output schema declared.

No examples provided.

mcp_sensor_config ~138

Configure a named sensor on `agent`. A sensor runs a script and its output is the reading. `script` is "<script-file> [args...]": a bare filename in the agent's scripts/ folder (no paths - that folder is the only allowed location), with letters/digits-only arguments. On a Raspberry Pi it is a shell script run with `sh`; on a Pico or ESP32 a .py file the agent execs in-process. Pass remove=true to delete the sensor.

NameTypeReqDescription
agentstringyes–
namestringyes–
removeboolean––
scriptstring––

No output schema declared.

No examples provided.

mcp_sensor_read ~104

Read sensors on `agent`. With no `name`, reads every configured sensor and returns them merged into one JSON object; with a `name`, reads just that sensor. Every reading is nested under its sensor's own name: a script emitting a JSON object with several fields nests whole, one emitting a single-field object contributes just that field's value, and any other output is wrapped the same way.

NameTypeReqDescription
agentstringyes–
namestring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.ctrlpi/ctrlpi-mcp server?

io.github.ctrlpi/ctrlpi-mcp runs locally as an npm package, launched with npx -y ctrlpi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ctrlpi-mcp

# add to Claude Code
claude mcp add ctrlpi-ctrlpi-mcp -- npx -y ctrlpi-mcp
Common questions

What is the io.github.ctrlpi/ctrlpi-mcp server?

io.github.ctrlpi/ctrlpi-mcp is listed in the public MCP registry as io.github.ctrlpi/ctrlpi-mcp. MCP server to control Raspberry Pi, Pico W and ESP32 GPIO agents from an AI assistant. This page covers its npm package (ctrlpi-mcp).

Is the io.github.ctrlpi/ctrlpi-mcp server safe to use?

io.github.ctrlpi/ctrlpi-mcp scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.ctrlpi/ctrlpi-mcp server expose?

io.github.ctrlpi/ctrlpi-mcp exposes 18 tools: mcp_agents_list, mcp_gpio_read, mcp_gpio_write, mcp_gpio_scan, mcp_gpio_config, and 13 more. Their descriptions and schemas cost roughly 1,878 tokens of context every time the server is loaded.

Is the io.github.ctrlpi/ctrlpi-mcp server still maintained?

io.github.ctrlpi/ctrlpi-mcp 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 io.github.ctrlpi/ctrlpi-mcp server under?

io.github.ctrlpi/ctrlpi-mcp declares the MIT 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 io.github.ctrlpi/ctrlpi-mcp server?

VerifyMCP ran 16 checks on io.github.ctrlpi/ctrlpi-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.