What this kind of tool is for
- Scan a repository or dependency tree for known vulnerabilities.
- Audit secrets, permissions, or headers during a pre-release review.
- Have your agent explain a suspicious script or config before you run it.
How to compare servers like this
- Failure mode:
- Vulnerability reports are probabilistic; read findings as leads to verify, not verdicts.
- Data leaving the box:
- Check whether files or code are uploaded anywhere before scanning anything private.
- Maintenance signal:
- Security rulesets age fast; stale tools miss new classes of issue.
- Report clarity:
- The best tools say what is wrong, how sure they are, and how to fix it — verify findings yourself.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the grim-mcp MCP server?
Security audit for AI agents: code, deps, exposure, secrets, drift, SBOM, and IoC.
How to install grim-mcp
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"grim-mcp": {
"command": "npx",
"args": [
"-y",
"grim-mcp"
]
}
}
}Related MCP servers
Repo rules enforcement for AI agents. Checks diffs against repo conventions.

Deterministic code analysis harness giving AI agents senses, memory and judgment for code.
View repository →Project memory across sessions for AI agents. A queryable decision log in the repo.
Reference integrity for AI agents. Scans and verifies links, imports, assets, deps.
Release intelligence for AI agents. Detects breaking changes and recommends semver.
Deployment truth verification for AI agents. Verifies the live site matches the build.