Heimdall — Mcp Security Scanner
@caglarbozkurt
About Heimdall — Mcp Security Scanner
Security scanner for MCP servers — vet an MCP before you wire it into an agent. Detects prompt-injection, credential exfiltration (via taint analysis), RCE, and supply-chain risks, and catches cross-server exfil chains no single server reveals. Zero-dependency local CLI, SARIF ou
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"heimdall": {
"command": "npx",
"args": [
"-y",
"--package",
"mcp-heimdall-scan",
"heimdall-mcp"
]
}
}
}Tools
1Statically vet an MCP server (or a whole MCP client config) BEFORE trusting or installing it. Checks prompt-injection / tool-poisoning, risky capabilities (fs/network/shell/eval/credentials), proven data-exfiltration paths, dependency CVEs, provenance, and multi-server composition. Returns a pass/warn/fail verdict with cited evidence. Static analysis only — downloads the package but does NOT execute it. Use it when the user is about to add/connect an MCP server.
Overview
What is Heimdall — Mcp Security Scanner?
Heimdall is a local, pre-flight security scanner for Model Context Protocol (MCP) servers. It vets a single server or an entire agent configuration before an agent trusts it, without running the server by default, and requires no account or backend.
How to use Heimdall — Mcp Security Scanner?
Use the CLI via npx mcp-heimdall-scan <target> or install globally. Targets include npm/PyPI packages, local directories, git repositories, a tools/list dump, or an MCP client config file (e.g., claude_desktop_config.json). Options like --policy, --online, --json, and --sarif customize the scan. It also ships as a GitHub Action and as an MCP server itself.
Key features of Heimdall — Mcp Security Scanner
- Static analysis without executing server code.
- Detects injection, capability, exfiltration, provenance, and CVEs.
- Proven data-flow paths for JS/TS (file:line evidence).
- Audits whole agent configs for cross-server exfiltration chains.
- Policy-based verdicts (default, strict, custom waivers with expiry).
- Runs entirely locally, no account or backend needed.
Use cases of Heimdall — Mcp Security Scanner
- Vet a server package before installing it in your agent.
- Audit your entire MCP client config (e.g.,
claude_desktop_config.json) for cross-server risks. - Gate pull requests in CI using the GitHub Action to fail on risky servers.
- Use the MCP server mode to let your agent scan a server before connecting to it.
- Run behavioral validation (
heimdall validate) in a disposable VM to check static findings against runtime behavior.
FAQ from Heimdall — Mcp
Basic information
More Developer Tools MCP servers

Skilder.ai
skilder.aiRun skills and MCP tools like production software: versioned, composed into roles, distributed to every agent from one governed library.
SecondSim
econdSim provisions real UK mobile numbers (non-VoIP) via eSIM, built for freelancers, sole traders, small businesses, and enterprise teams. Unlike VoIP apps and virtual numbers, SecondSim numbers register as genuine phy
Vibgrate MCP
VibgrateQuery your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up
OrangePro
Aamir SiddiquiOrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.
LocalCan
LocalCanGives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.
Comments