Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP
NPM · RASPBERRY-PI-CONNECT-MCP
Raspi Connect MCP: shell access to Raspberry Pi devices via Raspberry Pi Connect web shell
Available components
Last scanned (21 hours ago)
Scores higher than 53% of npm servers
Category IoT and Hardware
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to kritzerenkrieg/raspberry-pi-connect-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 585 tokens (~73/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_keys" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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
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 →
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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 −3
- Malware scan: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: kritzerenkrieg/raspberry-pi-connect-mcp security
- Schema quality: 376 → 585 ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.1 → 0.2.0 functional
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 26 48
First indexed and scored.
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/raspberry-pi-connect-mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | kritzerenkrieg/raspberry-pi-connect-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/kritzerenkrieg/raspberry-pi-connect-mcp/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 3970424454 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:838a3d2e10140dc53bafcd710069cd45974eb42843dfb29e1dcd991f97b0d88ca07cf919531eb19ac10a7fc9a920e4fe30fccb2070c48e985fd99ae7c |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
account ~42
Show which Raspberry Pi Connect account is signed in (email when it can be read), when the session was saved, its device names, and whether a login is in progress.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
close_session ~42
Close the remote shell session to a device.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device name (or unique substring of it) or device UUID, as shown by list_devices |
No output schema declared.
No examples provided.
list_devices ~26
List devices on the Raspberry Pi Connect account with online status and whether remote shell is allowed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login ~108
Sign in to Raspberry Pi Connect: opens a Chrome window on this computer where the USER signs in by hand (tell them to do so). Waits up to wait_sec for it; if still in progress, call account later. fresh=true signs out the current account first (switch account). The new session is used right away.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Sign out first (current session backed up), to switch account |
| wait_sec | integer | – | Seconds to wait for the user to finish |
No output schema declared.
No examples provided.
logout ~59
Sign out of Raspberry Pi Connect. The session and Chrome profile are moved to a backup folder (old-account_<time>) so the account can be restored, or deleted with delete=true.
| Name | Type | Req | Description |
|---|---|---|---|
| delete | boolean | – | Delete the session instead of backing it up |
No output schema declared.
No examples provided.
read_screen ~68
Read the current terminal screen (plus a little scrollback) of a device shell.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device name (or unique substring of it) or device UUID, as shown by list_devices |
| lines | integer | – | Last N lines (0 = screen + 20 lines) |
No output schema declared.
No examples provided.
run_command ~130
Run a shell command on a device through its Connect remote shell and return output + exit code. The shell session persists between calls (cwd, env vars). First call to a device takes ~30s to connect. Commands that wait for input (sudo password, editors, confirmations) will time out; use send_keys/read_screen for those.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Shell command line (bash) to run |
| device | string | yes | Device name (or unique substring of it) or device UUID, as shown by list_devices |
| timeout_sec | integer | – | Max seconds to wait for completion |
No output schema declared.
No examples provided.
send_keys ~110
Send raw keystrokes to a device shell (for interactive programs). Supports escapes: "\n" Enter, "\x03" Ctrl-C, "\x04" Ctrl-D, "\t" Tab, "\x1b" Esc, "\x1b[A" Up. Returns the current screen.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device name (or unique substring of it) or device UUID, as shown by list_devices |
| keys | string | yes | Keys to send; JSON-style escapes are interpreted |
No output schema declared.
No examples provided.
How do I install the Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP server?
Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP runs locally as an npm package, launched with npx -y raspberry-pi-connect-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 · raspberry-pi-connect-mcp
claude mcp add kritzerenkrieg-raspberry-pi-connect-mcp -- npx -y raspberry-pi-connect-mcp
What is the Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP server?
Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP is listed in the public MCP registry as io.github.kritzerenkrieg/raspberry-pi-connect-mcp. Raspi Connect MCP: shell access to Raspberry Pi devices via Raspberry Pi Connect web shell. This page covers its npm package (raspberry-pi-connect-mcp).
Is the Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP server safe to use?
Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP server expose?
Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP exposes 8 tools: list_devices, run_command, send_keys, read_screen, close_session, and 3 more. Their descriptions and schemas cost roughly 585 tokens of context every time the server is loaded.
Is the Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP server still maintained?
Raspberry Pi Connect (Raspi Connect / RPi Connect) 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 Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP server under?
Raspberry Pi Connect (Raspi Connect / RPi Connect) 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 Raspberry Pi Connect (Raspi Connect / RPi Connect) MCP server?
VerifyMCP ran 16 checks on Raspberry Pi Connect (Raspi Connect / RPi Connect) 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.