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.Reachpad/reachpad-mcp

NPM · @REACHPAD/MCP · 2 COMPONENTS · SCANNED AUG 16

Persistent cloud development environments that coding agents create, run and test software in.

73 Trust /100
Trust breakdown (6 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 →

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 & Transparency84
  • 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
  • License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 4 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 439 tokens (~73/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @reachpad/mcp

# add to Claude Code
claude mcp add reachpad-reachpad-mcp -- npx -y @reachpad/mcp
# add to Codex CLI
codex mcp add reachpad-reachpad-mcp -- npx -y @reachpad/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reachpad-reachpad-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reachpad/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add reachpad-reachpad-mcp --command npx --arg -y --arg @reachpad/mcp
# ~/.hermes/config.yaml
mcp_servers:
  reachpad-reachpad-mcp:
    command: "npx"
    args: ["-y", "@reachpad/mcp"]
// mcp.json
{
  "mcpServers": {
    "reachpad-reachpad-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@reachpad/mcp"
      ]
    }
  }
}
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.

  • 16 Aug 26 0
    • Security disclosure: fail → unverified functional
  • 12 Aug 26 73

    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 16 Aug 2026 · Analysed npm/@reachpad/mcp@0.1.4

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.1.4
Rekor log index 2431053838
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:1989d61d0403680a3747c77d755c1e3fc565f4f227847fc94dab66ce4ee889ac5179eb9f966447d48c4f865fd416940a6e1c8af59affa8bf9966a20e4
Dependencies 0 packages
Packages resolved 0
Tree resolution Complete
MCP tools · 6 exposed · ~439 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.

Tool Tokens
checkpoint_environment ~66

Fork an environment 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.

NameTypeReqDescription
environmentstringyes
namestringName for the fork.

No output schema declared.

No examples provided.

create_environment ~103

Create a persistent development environment: a filesystem and processes that survive between calls. Optionally clone a git repository into it. Returns the environment id used by every other tool.

NameTypeReqDescription
namestringyesHuman-readable name, e.g. the repo or task.
refstringOptional branch or tag to check out.
repostringOptional git URL to clone into /work. Must be reachable without credentials unless the account has a mirror for it.

No output schema declared.

No examples provided.

delete_environment ~49

Archive an environment, 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.

NameTypeReqDescription
environmentstringyes

No output schema declared.

No examples provided.

get_environment ~47

What an environment resumes from: its head snapshot, whether that snapshot carries memory (resumes mid-process) or only disk (boots), and its fork tree.

NameTypeReqDescription
environmentstringyes

No output schema declared.

No examples provided.

list_environments ~22

List this account's environments, with how many forks each has.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

run_command ~152

Run one command in an environment 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 environment resumes to serve this.

NameTypeReqDescription
argvarrayyes
cwdstring
envobject
environmentstringyes
timeout_msintegerGive up after this long. PASS IT. Clamped by the entitlement server-side, and without it the environment is allowed ten minutes — so a wedged environment costs you ten before you learn anything. Seco…

No output schema declared.

No examples provided.