Is XRPName MCP server safe?
Yes, with the usual care.
Passed every safety check we run. Maintained, authenticated, reachable, clean scan.
What to know before installing
- highWrite-action tools reachable without authentication
How XRPName compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 87/100
- higher than 73% of 48,255 servers
- Tools that change things
- 10%
- 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: 7 read · 1 create · 2 change
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
1 high
- Code scan56 source files scanned25/25
- Live reliabilityremote reachable in 1014ms20/20
- Tool poisoning10 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 5 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON