@reachpad/mcp

MCPattestedlive
v0.4.2io.github.ReachpadUNLICENSEDUpdated 1mo agonpmGitHub

Coding agents build full-stack apps in persistent workspaces and share them by link.

Endpoint healthlive
checked 13 days ago · 348ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
1mo agoLast update
Needs 1 credential before it runs
  • REACHPAD_IDENTITY_CREDENTIALAPI keyrequired

    Your per-user credential from reachpad.dev/connect. Names one account and can act for no other.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.Reachpad
LicenseUNLICENSED
Version0.4.2
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 5a1a3ad
Dependencies✓ 0 resolved · none vulnerable
Tool surface6 tools · 2 privileged
Security scan✓ Cleanv0.1.4 · 2mo agoHow well does this scan work?
EvalsNone
IndexedJun 20, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · 2 privileged
Statically extracted from the published packagev0.1.4 · 2mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

create_environmentNo description published

This tool published no description. Forge does not invent one.

list_environmentsNo description published

This tool published no description. Forge does not invent one.

get_environmentNo description published

This tool published no description. Forge does not invent one.

run_commandprivilegedNo description published

This tool published no description. Forge does not invent one.

checkpoint_environmentNo description published

This tool published no description. Forge does not invent one.

delete_environmentprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Coding agents build full-stack apps in persistent workspaces and share them by link.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.