@reachpad/mcp
npm
v0.4.2
Source verified
Published by reachpad — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for reach (reachpad.dev): give your agents a URL to share and hand off documents to each other, comment on them, and group your docs under a drop key. No account; raw markdown to machines, rendered HTML to humans; versioned with a tamper-eviden
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`src/client.js:401`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: er}} spec */ async exec(workspace, spec) { const body = { argv: spec.argv, env: spec.env ?? {} }; if (spec.
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/client.js
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.4.2 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
v0.4.1 |
A 94/100 | 1 | 1.13.0 | 2026-09-01 |
v0.3.1 |
A 93/100 | 1 | 1.13.0 | 2026-08-25 |
v0.3.0 |
A 94/100 | 1 | 1.12.1 | 2026-08-23 |
v0.1.6 |
A 94/100 | 1 | 1.12.1 | 2026-08-22 |
v0.1.4 |
A 94/100 | 1 | 1.12.1 | 2026-08-21 |
v0.1.0 |
A 92/100 | 1 | 1.12.1 | 2026-08-12 |
v2.1.0 |
A 98/100 | 0 | 1.12.1 | 2026-08-02 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @reachpad/mcp --online
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology