AI Agent Firewall vs Frappe Inspector
These two are level on the tashan score (within 1 points), so the score does not decide it. The evidence rows below are where they differ. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›
| AI Agent Firewall | Frappe Inspector | what it means | |
|---|---|---|---|
| tashan score | 70 | 69 | upkeep + freshness, gated by adoption |
| Adoption evidence | 3k/wk | 2k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 72 | 66 | cadence, maintainers, status |
| Expertise grade | solid | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, runs an install script, no build provenance | no known advisories, no build provenance | a summary — the full audit, free, is on each dossier |
| Licence | — | — | |
| Maintainers | one primary | one primary | bus-factor risk |
Install either
AI Agent Firewall
claude mcp add ai-agent-firewall -- npx -y @fidacy/mcpFrappe Inspector
claude mcp add frappe-inspector -- npx -y @frappe-inspector/mcpNeither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each — the advisory ids, the version that fixes them and anything that runs at install time — is free on its own page: AI Agent Firewall · Frappe Inspector.