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/bmdhodl/agent47Wrote 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/bmdhodl/agent47/agentguard47)<a href="https://agentmods.dev/mcp/bmdhodl/agent47/agentguard47"><img src="https://agentmods.dev/badge/mcp/bmdhodl/agent47/agentguard47/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/bmdhodl/agent47/agentguard47"><img src="https://agentmods.dev/badge/mcp/bmdhodl/agent47/agentguard47.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentguard47 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 1mo 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.
What it actually says
{
"agentguard47": {
"command": "npx",
"args": [
"-y",
"@agentguard47/mcp-server"
],
"env": {
"AGENTGUARD_API_KEY": "",
"AGENTGUARD_URL": ""
}
}
}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.
- 1mo ago First seen · 13 lines scan A 48698391821a
agentguard47 is an MCP server published in the GitHub repository bmdhodl/agent47 (4 stars, last pushed today), 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
qorami
Check an email before an AI agent sends it: send / ask a human / block. Detects prompt injection. Runs locally from the qorami-mcp npm package. Needs 1 environment variable to run.
agentsgate
AI Agent I/O Tracking & Rollback System — MCP Proxy Gateway. Runs locally from the agentsgate npm package.
sentinel-ai
MCP server "sentinel-ai" as configured in MaxwellCalkin/sentinel-ai. Runs sentinel.mcp_server with python.
shield
MCP server "shield" as configured in kobepaw/goop-shield-community. Launched with goop-shield mcp --port 8787.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
thumbgate
MCP server "thumbgate" as configured in IgorGanapolsky/ThumbGate. Runs adapters/mcp/server-stdio.js with node.