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

NPM · PI-BAY

App and MCP server for Raspberry Pis and SSH devices on a LAN: files, terminal, ctrlPi API install.

Available components

71 Trust /100

Last scanned (22 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 Security98
  • 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
  • 5 of 10 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1274 tokens (~98/item across 13 items; 13 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 Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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 14 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/pi-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 10 packages
Packages resolved 10
Stale 5
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,241 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
pi_command_run ~90

Execute a shell command on the remote device via SSH. Returns stdout, stderr, and exit_code.

NameTypeReqDescription
commandstringyesShell command line to execute.
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
timeout_msinteger–Execution timeout in milliseconds (default 30000, max 300000).

No output schema declared.

No examples provided.

pi_ctrlpi_install ~265

Install or update pi-gpio-api (the ctrlPi API agent) in ~/pi-gpio-api with its install.sh. On a first install, name and api_key are written to ~/pi-gpio-api/config.json (defaults: the device hostname and your-secret-key, the installer's own); an existing config.json is kept and they are ignored. A result with the default key carries a warning. On a Raspberry Pi with passwordless sudo the pi-gpio-api service is then created and started, or restarted; otherwise service is needs_sudo and output holds the sudo commands to run. Can take several minutes (the full package installs FastAPI). Ask the user first and pass confirmed: true.

NameTypeReqDescription
api_keystring–Agent API key for a first install. Default: your-secret-key (public, so change it).
confirmedbooleanyesMust be true after the user explicitly confirms the install.
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
namestring–Agent name for a first install. Default: the device hostname.
packagestring–lite: the dependency-free server (recommended). full: FastAPI with /docs pages.

No output schema declared.

No examples provided.

pi_device_authenticate ~106

Authenticate to a Raspberry Pi or SSH device, verify credentials, cache the connection, and optionally save the password to the system keychain.

NameTypeReqDescription
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
passwordstringyesSSH password.
save_passwordboolean–Save password to macOS Keychain or Linux Secret Service.
usernamestring–SSH username (defaults to "pi").

No output schema declared.

No examples provided.

pi_device_info ~58

Get detailed hardware model, operating system, storage, memory, uptime, and ctrlPi information for a device.

NameTypeReqDescription
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.

No output schema declared.

No examples provided.

pi_device_reboot ~47

Reboot the remote Raspberry Pi or SSH device.

NameTypeReqDescription
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.

No output schema declared.

No examples provided.

pi_devices_list ~55

Scan the local network for Raspberry Pis and SSH devices, returning IP, MAC, hostname, model, ctrlPi status, and saved credential availability.

NameTypeReqDescription
force_refreshboolean–Rescan the network instead of using cached results.

No output schema declared.

No examples provided.

pi_directory_create ~65

Create a directory on the remote device relative to $HOME.

NameTypeReqDescription
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
pathstringyesPath relative to the authenticated user's remote $HOME directory.

No output schema declared.

No examples provided.

pi_file_read ~87

Read one file from the remote device relative to $HOME. auto returns UTF-8 text when safe and base64 for binary data.

NameTypeReqDescription
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
encodingstring––
pathstringyesPath relative to the authenticated user's remote $HOME directory.

No output schema declared.

No examples provided.

pi_file_write ~113

Create or overwrite one file on the remote device relative to $HOME, creating missing parent directories. content may be UTF-8 text or base64 and is limited to 16 MB.

NameTypeReqDescription
contentstringyesFile content (UTF-8 or base64).
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
encodingstring––
pathstringyesPath relative to the authenticated user's remote $HOME directory.

No output schema declared.

No examples provided.

pi_files_list ~81

List files and directories on the remote device relative to $HOME.

NameTypeReqDescription
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
pathstring–Path relative to the authenticated user's remote $HOME directory.
show_hiddenboolean–Include hidden files (starting with .).

No output schema declared.

No examples provided.

pi_path_delete ~72

Permanently delete one file or recursively delete one directory on the remote device relative to $HOME.

NameTypeReqDescription
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
pathstringyesPath relative to the authenticated user's remote $HOME directory.

No output schema declared.

No examples provided.

pi_path_rename ~87

Rename or move one file or directory on the remote device relative to $HOME.

NameTypeReqDescription
device_idstringyesIP address, hostname, MAC address, or device identifier of the target Raspberry Pi / SSH device.
fromstringyesPath relative to the authenticated user's remote $HOME directory.
tostringyesPath relative to the authenticated user's remote $HOME directory.

No output schema declared.

No examples provided.

pi_ui ~115

Open the pi-bay web UI (devices, files, terminal) in the browser, starting its web server when needed (action open, the default). When pi-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 pi-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/pi-bay MCP server?

io.github.ctrlpi/pi-bay runs locally as an npm package, launched with npx -y pi-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 · pi-bay

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

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

io.github.ctrlpi/pi-bay is an MCP server listed in the public MCP registry as io.github.ctrlpi/pi-bay. App and MCP server for Raspberry Pis and SSH devices on a LAN: files, terminal, ctrlPi API install. This page covers its npm package (pi-bay).

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

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

io.github.ctrlpi/pi-bay exposes 13 tools: pi_devices_list, pi_device_info, pi_device_authenticate, pi_command_run, pi_files_list, and 8 more. Their descriptions and schemas cost roughly 1,241 tokens of context every time the server is loaded.

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

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

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

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