Is Crixin Voice MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highRemote endpoint did not respond — HTTP 503
- highRepository is archived
How Crixin Voice compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 46/100
- higher than 9% of 48,114 servers
- Uptime
- 0%
- of our recent checks; the typical remote server answers 100%
Public scan report
scanner v0.1.10 · 2026-10-12 · same rubric, same numbers if you re-run it
2 high
- Code scan154 source files scanned25/25
- Live reliabilityremote unreachable: HTTP 5030/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancerepository archived0/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Findings (2)
- highRemote endpoint did not respond
reliability.unreachableHTTP 503
- highRepository is archived
maint.archived
Overall 46/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Safer options for the same job
- treg.toOpenRouter for tools and data. Compare catalog providers and call them from one hosted MCP endpoint.not reviewedEstablishedA
