Is Reachpad MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
What to know before installing
- highWrite-action tools reachable without authentication
How Reachpad compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,243 servers
- Tools that change things
- 32%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
What its tools let an agent do: 13 read · 1 create · 6 change · 3 delete · 2 send or post
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
1 high
- Code scan8 source files scanned25/25
- Live reliabilityremote reachable in 835ms20/20
- Tool poisoning25 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 8 write-action tools with no auth3/15
- Maintenancelast push 54 days ago12/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Reachpad does
Compiler ExplorerCompile code with thousands of compilers, inspect the assembly, and share godbolt.org linksnot reviewedEstablishedB