Is Audit AI MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
How Audit AI compares
Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 55% of 802 Databases servers
- Tools that change things
- 0%
- typical: 10%. Fewer write tools means less an agent can break
What its tools let an agent do: 7 read
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
1 medium
- Code scan2 source files scanned20/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 qualitylocal package, no credentials required12/15
- Maintenancelast push 10 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/auditai-mcp.mjs: …s("Cloudflare")) return false; try { new Function(""); return true; } catch (_) { ret…
Overall 82/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 Audit AI does
- InfrawiseLive AWS, database & Kafka infrastructure context for AI coding assistants via MCP.not reviewedGrowingA
- JanuscopeLocal MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.not reviewedGrowingA
- legacy2mcpTurn a legacy SOAP/WSDL, database, or REST API into a safe, typed, audit-logged MCP servernot reviewedGrowingA