io.github.Reachpad/reachpad-mcp
NPM · @REACHPAD/MCP · 2 COMPONENTS
Coding agents build full-stack apps in persistent workspaces and share them by link.
Available components
Last scanned (18 hours ago)
Scores higher than 94% of npm servers
Category Developer Tools
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Reachpad/reachpad-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 44 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 859 tokens (~78/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 37% 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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −2
- Stability: pass → 0.83 functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 16 Oct 2026 · Analysed npm/@reachpad/mcp@0.4.2
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 | Reachpad/reachpad-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Reachpad/reachpad-mcp/.github/workflows/publish.yml@refs/tags/v0.4.2 |
| Rekor log index | 2683053486 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7e88c80d8e3f1861b6febb88b9e6e8b79025ce640bc5a89e6890ba14b53a553995335918d497e4c87251a15a171a594b82c680c921d3aa5bc50e6ef82 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
checkpoint_workspace Fork workspace ~66
Fork a workspace from its last sealed snapshot into a new one. The original is untouched. This is how you try several approaches from one prepared state — the fork costs a delta, not a rebuild.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Name for the fork. |
| workspace | string | yes | – |
No output schema declared.
No examples provided.
create_workspace Create workspace ~107
Create a persistent development workspace: a filesystem and processes that survive between calls. Optionally clone a git repository into it. Returns the workspace id used by every other tool.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional display name. Reachpad generates one when omitted. |
| ref | string | – | Optional branch or tag to check out. |
| repo | string | – | Optional git URL to clone into `$HOME/work` inside the workspace. Must be reachable without credentials unless the account has a mirror for it. |
No output schema declared.
No examples provided.
delete_workspace Archive workspace ~71
Archive a workspace, freeing the plan slot it holds. Nothing is deleted: its snapshots and history survive, it simply stops counting as live and can no longer be used. A RUNNING workspace cannot be archived — pause_workspace first, or this is refused with `lease_held`.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | – |
No output schema declared.
No examples provided.
expose_port Expose a port to the web ~132
Open a port inside a workspace and get back a link that reaches it. This is how something you built becomes something a person can open. Idempotent per port: re-running it returns the link the port already has.
| Name | Type | Req | Description |
|---|---|---|---|
| check | boolean | – | Dial the port inside the workspace afterwards and say whether anything answered. Default true. It costs one short command, and it RESUMES the workspace if it was paused — pass false if you are openin… |
| port | integer | yes | The port your app is listening on INSIDE the workspace. |
| workspace | string | yes | – |
No output schema declared.
No examples provided.
get_credit_balance Get compute-credit balance ~35
Show this account's remaining compute credits. One credit runs one standard workspace for one minute; paused workspaces use no compute credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_workspace Inspect workspace ~56
What a workspace resumes from: its head snapshot, how far its log had got, and its fork tree. Every start is a cold boot from the head snapshot: files survive, running processes do not.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | – |
No output schema declared.
No examples provided.
list_ports List exposed ports ~46
The ports this workspace has open to the web, oldest first, with their links. Revoked ports are not listed: a closed link never comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | – |
No output schema declared.
No examples provided.
list_workspaces List workspaces ~23
List this account's workspaces, with how many forks each has.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause_workspace Pause workspace ~96
Save the workspace's disk and stop the meter. Files survive; RUNNING PROCESSES DO NOT — a paused workspace cold-boots, so anything you started with run_command has to be started again. The next run_command resumes it automatically. Pause when you are done: a running workspace spends a credit a minute whether or not anything is happening in it, and it cannot be archived while it runs.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | – |
No output schema declared.
No examples provided.
revoke_port Close an exposed port ~75
Close one port to the web. The link stops working at the visitor’s next request. NOT reversible in the way callers expect: re-opening the same port later mints a DIFFERENT link, so revoke only when the people holding the current one should lose it.
| Name | Type | Req | Description |
|---|---|---|---|
| port | integer | yes | – |
| workspace | string | yes | – |
No output schema declared.
No examples provided.
run_command Run a command ~152
Run one command in a workspace and get its exit code and output. Not a shell: pass argv as a list, and ask for a shell explicitly with ["/bin/sh","-lc","…"] if you want one. A paused workspace resumes to serve this.
| Name | Type | Req | Description |
|---|---|---|---|
| argv | array | yes | – |
| cwd | string | – | – |
| env | object | – | – |
| timeout_ms | integer | – | Give up after this long. PASS IT. Clamped by the entitlement server-side, and without it the workspace is allowed ten minutes — so a wedged workspace costs you ten before you learn anything. Seconds… |
| workspace | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.Reachpad/reachpad-mcp server?
io.github.Reachpad/reachpad-mcp runs locally as an npm package, launched with npx -y @reachpad/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 · @reachpad/mcp
claude mcp add reachpad-reachpad-mcp -- npx -y @reachpad/mcp
What is the io.github.Reachpad/reachpad-mcp server?
io.github.Reachpad/reachpad-mcp is listed in the public MCP registry as io.github.Reachpad/reachpad-mcp. Coding agents build full-stack apps in persistent workspaces and share them by link. This page covers its npm package (@reachpad/mcp).
Is the io.github.Reachpad/reachpad-mcp server safe to use?
io.github.Reachpad/reachpad-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 io.github.Reachpad/reachpad-mcp server expose?
io.github.Reachpad/reachpad-mcp exposes 11 tools: get_credit_balance, create_workspace, list_workspaces, get_workspace, run_command, and 6 more. Their descriptions and schemas cost roughly 859 tokens of context every time the server is loaded.
Is the io.github.Reachpad/reachpad-mcp server still maintained?
io.github.Reachpad/reachpad-mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 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.Reachpad/reachpad-mcp server under?
io.github.Reachpad/reachpad-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.