Is ChainRPC 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
- highRemote endpoint did not respond — HTTP 530
How ChainRPC MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 71/100
- higher than 34% of 48,114 servers
- Uptime
- 0%
- of our recent checks; the typical remote server answers 100%
Public scan report
scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it
1 high
- Code scan11 source files scanned25/25
- Live reliabilityremote unreachable: HTTP 5300/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableHTTP 530
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON