Is Prior MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highRemote endpoint did not respond — TypeError: fetch failed
How Prior compares
Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 58/100
- higher than 11% of 3,470 Web search servers
- Uptime
- 0%
- of our recent checks; the typical remote Web search server answers 100%
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
1 high
- Code scan11 source files scanned25/25
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 150 days ago8/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
Overall 58/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 Prior does
- Sui Knowledge Base (kapa.ai)Semantic search across Sui documentation and knowledge sources, powered by kapa.ainot reviewedEstablishedA
DocsMintCloud or self-hosted knowledge for AI agents: hybrid search, reranking, GraphRAG, scoped MCP tools.not reviewedEstablishedA- not reviewedEstablishedA
