Is Aifp MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
How Aifp compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 60/100
- higher than 15% of 48,255 servers
- Tools that change things
- 6%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 28 read · 1 create · 3 change · 1 send or post
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
2 medium
- Code scan36 source files scanned15/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 76 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (2)
- mediumnpm install lifecycle script present
install.script - mediumnpm install lifecycle script present
install.scriptpackage.json: …"tsc", "prepublishOnly": "tsc", "postinstall": "node scripts/postinstall.mjs", "bu…
Overall 60/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 Aifp does
- Deja Vudeja-vu: local memory over the session histories of forty-three coding agents.not reviewedEstablishedA
MemorixLocal-first project memory with legacy MCP and 2026 discovery compatibility.not reviewedEstablishedB- Nautilus Compass MemoryLocal-first long-term memory for AI agents, with byte-recomputable signed verification receipts.not reviewedEstablishedB