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/pico-bay

NPM · PICO-BAY

App and MCP server for Raspberry Pi Pico and ESP32 boards over USB: files, console, firmware.

Available components

71 Trust /100

Last scanned (14 hours ago)

Scores higher than 42% of npm 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 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 Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1478 tokens (~105/item across 14 items; 14 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 Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 81% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 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 (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 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.9.40 → 0.9.41 functional
  • 17 Nov 26 69

    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/pico-bay@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 · 14 exposed · ~1,447 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
pico_board_bootloader ~120

Restart the selected board into firmware install mode: BOOTSEL on a Pico, ROM download mode on an ESP32. The running program stops and the board leaves its normal serial port, so ask the user first. When an ESP32 cannot be reset automatically the result has manual: true and a reason, and the user must hold BOOT while pressing RESET. Afterwards call pico_boards_list, then pico_install with action check.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.

No output schema declared.

No examples provided.

pico_board_interrupt ~47

Send Ctrl-C to interrupt the program currently running on the selected board.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.

No output schema declared.

No examples provided.

pico_board_reset ~57

Soft-reset the selected board, or hard-reset it when the firmware supports hard reset.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
modestring––

No output schema declared.

No examples provided.

pico_boards_list ~41

List connected Raspberry Pi Pico and ESP32 boards with MicroPython or CircuitPython and report their capabilities. Use board_id from this result in every other tool.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pico_ctrlpi_install ~309

Install or update the ctrlPi API agent on a Pico W, Pico 2 W or an ESP32 running MicroPython (pico-gpio-api or esp32-gpio-api, downloaded from GitHub; the ESP32 agent officially supports the ESP32, ESP32-S3, ESP32-C3 and ESP32-C6; other ESP32 chips are allowed but not officially supported). Writes app.mpy, upgrader.mpy and main.py (plus boot.py on an ESP32), then config.json (the board's own kept, with this api_key and name), wifi.txt and scripts/cpu-temp.py when missing, and resets the board. It replaces main.py, so ask the user first and pass confirmed: true.

NameTypeReqDescription
api_keystring–Agent API key. Left out: the board's own key, else your-secret-key (public, so change it).
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
confirmedbooleanyesMust be true after the user explicitly confirms the install.
namestring–Agent name. Left out: the board's own name, else the agent's pico-<serial4> or esp32-<serial4> default; an empty string resets it to that default.
wifi_passwordstring–Wi-Fi password (empty for an open network).
wifi_ssidstringyesWi-Fi network the agent joins.

No output schema declared.

No examples provided.

pico_directory_create ~58

Create one directory on the selected board.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
pathstringyesPath on the board filesystem, relative to its root.

No output schema declared.

No examples provided.

pico_file_read ~89

Read one board file. auto returns UTF-8 text when safe and base64 for binary data; utf8 forces text; base64 always returns base64.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
encodingstring––
pathstringyesPath on the board filesystem, relative to its root.

No output schema declared.

No examples provided.

pico_file_write ~95

Create or overwrite one board file, creating missing parent directories. content may be UTF-8 text or base64 and is limited to 8 MB decoded.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
contentstringyes–
encodingstring––
pathstringyesPath on the board filesystem, relative to its root.

No output schema declared.

No examples provided.

pico_files_list ~76

List the complete board filesystem and report Flash and RAM usage. Hidden files (names starting with .) are omitted unless show_hidden is true.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
show_hiddenboolean–Include hidden files (starting with .).

No output schema declared.

No examples provided.

pico_install ~167

Install MicroPython on a Pico in BOOTSEL mode or a supported ESP32 in DOWNLOAD mode. Always call action check first. A Pico may require mounting and a Wi-Fi model choice. An ESP32 uses the detected chip-specific generic build. Obtain explicit confirmation before calling action install.

NameTypeReqDescription
actionstringyes–
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
confirmedboolean–Must be true after the user explicitly confirms installation.
firmwarestringyes–
initialize_storageboolean–Erase and initialize ESP32 filesystem storage during installation. Defaults to true for ESP32.
wifiboolean–Whether a Pico is a W model with Wi-Fi. Required only for Pico installation.

No output schema declared.

No examples provided.

pico_path_delete ~65

Permanently delete one file or recursively delete one directory from the selected board.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
pathstringyesPath on the board filesystem, relative to its root.

No output schema declared.

No examples provided.

pico_path_rename ~80

Rename or move one file or directory on the selected board.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
fromstringyesPath on the board filesystem, relative to its root.
tostringyesPath on the board filesystem, relative to its root.

No output schema declared.

No examples provided.

pico_python_run ~125

Run a Python file as __main__ or execute Python code. Provide exactly one of path or code. This can change any state accessible to code on the board. A program still running after timeout_ms is interrupted with Ctrl-C.

NameTypeReqDescription
board_idstringyesStable board UID returned by pico_boards_list, or its current serial device path.
codestring––
pathstring–Path on the board filesystem, relative to its root.
timeout_msinteger–Execution timeout in milliseconds (default 30000, max 600000).

No output schema declared.

No examples provided.

pico_ui ~118

Open the pico-bay web UI (files, console, backup, firmware install) in the browser, starting its web server when needed (action open, the default). When pico-bay runs on a Raspberry Pi or another remote machine it cannot open the user's browser: the result then has opened: false, and url is the address to open in a browser on the user's computer. Action stop stops a web server this tool started; the pico-bay app itself is never stopped.

NameTypeReqDescription
actionstring–open (default) or stop.

No output schema declared.

No examples provided.

Install

How do I install the io.github.ctrlpi/pico-bay MCP server?

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

npm · pico-bay

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

What is the io.github.ctrlpi/pico-bay MCP server?

io.github.ctrlpi/pico-bay is an MCP server listed in the public MCP registry as io.github.ctrlpi/pico-bay. App and MCP server for Raspberry Pi Pico and ESP32 boards over USB: files, console, firmware. This page covers its npm package (pico-bay).

Is the io.github.ctrlpi/pico-bay MCP server safe to use?

io.github.ctrlpi/pico-bay scores 71 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/pico-bay MCP server expose?

io.github.ctrlpi/pico-bay exposes 14 tools: pico_boards_list, pico_files_list, pico_file_read, pico_file_write, pico_directory_create, and 9 more. Their descriptions and schemas cost roughly 1,447 tokens of context every time the server is loaded.

Is the io.github.ctrlpi/pico-bay MCP server still maintained?

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

io.github.ctrlpi/pico-bay 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/pico-bay MCP server?

VerifyMCP ran 16 checks on io.github.ctrlpi/pico-bay, 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.