Policy-gated, audited SSH for Linux and Windows hosts: roles, approvals, and an audit log.
Nothing to run from here
Pico Bay is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
11
downloads a day
local
runs on your machine
971
downloads in 30d
What it does
App and MCP server for Raspberry Pi Pico and ESP32 boards over USB: files, console, firmware.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user pico-bay-mcp '--' npx -y @ctrlpi/pico-bay --mcp-stdio
# 2 — ask your agent for something these tools do
# pico_boards_list, pico_install, pico_files_list and 10 more
Pico Bay costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CTAll 3 servers
ctrlpi3 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Pico Bay as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user pico-bay-mcp '--' npx -y @ctrlpi/pico-bay --mcp-stdioReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| action | string | yes | — |
| firmware | string | yes | — |
| wifi | boolean | no | Whether a Pico is a W model with Wi-Fi. Required only for Pico installation. |
| initialize_storage | boolean | no | Erase and initialize ESP32 filesystem storage during installation. Defaults to true for ESP32. |
| confirmed | boolean | no | Must be true after the user explicitly confirms installation. |
List the complete board filesystem and report Flash and RAM usage. Hidden files (names starting with .) are omitted unless show_hidden is true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| show_hidden | boolean | no | Include hidden files (starting with .). |
Read one board file. auto returns UTF-8 text when safe and base64 for binary data; utf8 forces text; base64 always returns base64.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| path | yes | — | |
| encoding | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| path | yes | — | |
| content | string | yes | — |
| encoding | string | no | — |
Create one directory on the selected board.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| path | yes | — |
Rename or move one file or directory on the selected board.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| from | yes | — | |
| to | yes | — |
Permanently delete one file or recursively delete one directory from the selected board.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| path | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| path | no | — | |
| code | string | no | — |
| timeout_ms | integer | no | Execution timeout in milliseconds (default 30000, max 600000). |
Send Ctrl-C to interrupt the program currently running on the selected board.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — |
Soft-reset the selected board, or hard-reset it when the firmware supports hard reset.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| mode | string | no | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — |
Install or update the ctrlPi API agent on a Pico W, Pico 2 W, ESP32, ESP32-S3 or ESP32-C3 running MicroPython (pico-gpio-api or esp32-gpio-api, downloaded from GitHub). 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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board_id | yes | — | |
| api_key | string | no | Agent API key. Left out: the board's own key, else your-secret-key (public, so change it). |
| wifi_ssid | string | yes | Wi-Fi network the agent joins. |
| wifi_password | string | no | Wi-Fi password (empty for an open network). |
| name | string | no | 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. |
| confirmed | boolean | yes | Must be true after the user explicitly confirms the install. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Pico Bay or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.9.34 · scanned 9 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings3 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestc244169217b95cd4857af881d37a5e744b545778ba29475b80d11f8bf9426810
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| pico_boards_list | no tags | |
| pico_install | untrusted-inputstate-write | untrusted-input: keyword "download"; state-write: declares readOnlyHint: false, destructiveHint: true |
| pico_files_list | no tags | |
| pico_file_read | no tags | |
| pico_file_write | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| pico_directory_create | state-write | state-write: declares readOnlyHint: false |
| pico_path_rename | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| pico_path_delete | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| pico_python_run | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| pico_board_reset | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| pico_board_bootloader | untrusted-inputstate-write | untrusted-input: keyword "download"; state-write: declares readOnlyHint: false, destructiveHint: true |
| pico_ctrlpi_install | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc244169217b95cd4
Scanned2026-11-09
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.9.34. Pin a release below and the command asks for exactly that one.
0.9.34
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Pico Bay can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.