Is Memwyre MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highRemote endpoint did not respond — TypeError: fetch failed
How Memwyre compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 45/100
- higher than 8% 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-16 · same rubric, same numbers if you re-run it
1 high
- –Code scanremote-only server, no package to scann/a
- 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 31 days ago12/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
Overall 45/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
- Codebase MemoryCodebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.not reviewedWidely usedC
- Token SaviorStructural codebase MCP server with persistent memory: navigate by symbol, recall across sessions.not reviewedEstablishedA
- Neo4j MemoryMCP Neo4j Knowledge Graph Memory Servernot reviewedEstablishedB
