# io.github.ctrlpi/pico-bay (npm · pico-bay)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `pico-bay`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ctrlpi-pico-bay/pico-bay.md), [page](https://verifymcp.io/servers/ctrlpi-pico-bay/pico-bay)

## Channel facts

- Registry: `npm`
- Package: `pico-bay`
- Version: `0.9.41`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1478 tokens (~105/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 81% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add ctrlpi-pico-bay -- npx -y pico-bay --mcp-stdio
```

### Cursor

```json
{
  "mcpServers": {
    "ctrlpi-pico-bay": {
      "command": "npx",
      "args": [
        "-y",
        "pico-bay",
        "--mcp-stdio"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ctrlpi-pico-bay": {
      "command": "npx",
      "args": [
        "-y",
        "pico-bay",
        "--mcp-stdio"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ctrlpi-pico-bay -- npx -y pico-bay --mcp-stdio
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ctrlpi-pico-bay": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pico-bay",
        "--mcp-stdio"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  ctrlpi-pico-bay:
    command: "npx"
    args: ["-y", "pico-bay", "--mcp-stdio"]
```

### Netclaw

```json
{
  "McpServers": {
    "ctrlpi-pico-bay": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pico-bay",
        "--mcp-stdio"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "ctrlpi-pico-bay": {
      "command": "npx",
      "args": [
        "-y",
        "pico-bay",
        "--mcp-stdio"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 71, +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.

### 2026-11-19 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-18 (score 55, −14)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.9.40 → 0.9.41

### 2026-11-17 (score 69)

First indexed and scored.

## MCP tools (14)

### `pico_boards_list` (~41 tokens)

List connected boards

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.

### `pico_files_list` (~76 tokens)

List board files

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

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `show_hidden` (boolean): Include hidden files (starting with .).

### `pico_file_read` (~89 tokens)

Read a board file

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

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `encoding` (string)
- `path` (string, required): Path on the board filesystem, relative to its root.

### `pico_file_write` (~95 tokens)

Write a board file

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.

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `content` (string, required)
- `encoding` (string)
- `path` (string, required): Path on the board filesystem, relative to its root.

### `pico_directory_create` (~58 tokens)

Create a board directory

Create one directory on the selected board.

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `path` (string, required): Path on the board filesystem, relative to its root.

### `pico_path_rename` (~80 tokens)

Rename or move a board path

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

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `from` (string, required): Path on the board filesystem, relative to its root.
- `to` (string, required): Path on the board filesystem, relative to its root.

### `pico_path_delete` (~65 tokens)

Delete a board path

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

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `path` (string, required): Path on the board filesystem, relative to its root.

### `pico_python_run` (~125 tokens)

Run Python on a board

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.

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `code` (string)
- `path` (string): Path on the board filesystem, relative to its root.
- `timeout_ms` (integer): Execution timeout in milliseconds (default 30000, max 600000).

### `pico_board_interrupt` (~47 tokens)

Interrupt a board program

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

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.

### `pico_board_reset` (~57 tokens)

Reset a board

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

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `mode` (string)

### `pico_board_bootloader` (~120 tokens)

Put a board into firmware install mode

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.

Input parameters:

- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.

### `pico_ctrlpi_install` (~309 tokens)

Install the ctrlPi API on a board

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.

Input parameters:

- `api_key` (string): Agent API key. Left out: the board's own key, else your-secret-key (public, so change it).
- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `confirmed` (boolean, required): Must be true after the user explicitly confirms the install.
- `name` (string): 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_password` (string): Wi-Fi password (empty for an open network).
- `wifi_ssid` (string, required): Wi-Fi network the agent joins.

### `pico_ui` (~118 tokens)

Open or stop the pico-bay web UI

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.

Input parameters:

- `action` (string): open (default) or stop.

### `pico_install` (~167 tokens)

Install firmware on a bootloader-mode board

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.

Input parameters:

- `action` (string, required)
- `board_id` (string, required): Stable board UID returned by pico_boards_list, or its current serial device path.
- `confirmed` (boolean): Must be true after the user explicitly confirms installation.
- `firmware` (string, required)
- `initialize_storage` (boolean): Erase and initialize ESP32 filesystem storage during installation. Defaults to true for ESP32.
- `wifi` (boolean): Whether a Pico is a W model with Wi-Fi. Required only for Pico installation.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ctrlpi-pico-bay/pico-bay#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 55
- 2026-11-17: 69

## 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.

## Links

- npm package: https://www.npmjs.com/package/pico-bay
- Socket report: https://socket.dev/npm/package/pico-bay
- Repository: https://github.com/ctrlpi/pico-bay
- Website: https://ctrlpi.com/pico-bay
- Changelog RSS feed: https://verifymcp.io/servers/ctrlpi-pico-bay/pico-bay.xml
- Changelog JSON feed: https://verifymcp.io/servers/ctrlpi-pico-bay/pico-bay/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ctrlpi-pico-bay/pico-bay.json
- HTML version of this page: https://verifymcp.io/servers/ctrlpi-pico-bay/pico-bay
