Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/caglarbozkurt/mcp-heimdallWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/caglarbozkurt/mcp-heimdall/heimdall)<a href="https://agentmods.dev/mcp/caglarbozkurt/mcp-heimdall/heimdall"><img src="https://agentmods.dev/badge/mcp/caglarbozkurt/mcp-heimdall/heimdall/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/caglarbozkurt/mcp-heimdall/heimdall"><img src="https://agentmods.dev/badge/mcp/caglarbozkurt/mcp-heimdall/heimdall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
heimdall scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- heimdall — 100% identical, 0 lines differ
What it actually says
{
"heimdall": {
"command": "npx",
"args": [
"-y",
"mcp-heimdall-scan",
"mcp-heimdall-scan",
"heimdall-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 12 lines scan A c3f54ccd764a
heimdall is an MCP server published in the GitHub repository caglarbozkurt/mcp-heimdall (0 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
kakunin
X.509 identity, risk scoring, and audit logging for AI agents. MiCA + EU AI Act compliant. Runs locally from the @kakunin/mcp npm package. Needs 2 environment variables to run.
mcptoon
MCP server "mcptoon" as configured in activeing123/mcptoon. Launched with mcptoon serve.
cloud-audit
Open-source, read-only AWS security scanner. 110 checks across 25 services, 31 attack-chain rules, 64 IAM escalation methods (incl. lateral AssumeRole graph), Proof Mode exploitability verification, data perimeter and Bedrock AgentCore checks, Blast Radius CLI, Threat Feed, What-If simulator, AI-SPM, 6 compliance…
aiterm-mcp
Persistent terminals and one launcher for Claude, Codex, Grok, and Cursor harnesses. Runs locally from the aiterm-mcp npm package.
regula
MCP server "regula" as configured in kuzivaai/getregula. Runs locally from the regula-ai Python package.
sanctions-screening
Sanctions screening against OFAC SDN, company registry verification and trade-restriction checks. Remote server at hatchloop.dev.