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/cybercraftsolutionsllc/trust-gated-agent-exampleWrote 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/cybercraftsolutionsllc/trust-gated-agent-example/mcp-shield)<a href="https://agentmods.dev/mcp/cybercraftsolutionsllc/trust-gated-agent-example/mcp-shield"><img src="https://agentmods.dev/badge/mcp/cybercraftsolutionsllc/trust-gated-agent-example/mcp-shield.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-shield 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 7d 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
{ "mcp-shield": { "url": "https://mcp.craftedtrust.com/api/v1/mcp", "type": "streamable-http" } }
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.
- 7d ago First seen · 6 lines scan A 8a08ad880a8b
mcp-shield is an MCP server published in the GitHub repository cybercraftsolutionsllc/trust-gated-agent-example (0 stars, last pushed 5mo 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
agent-security-scanner-mcp
Security layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities. Runs locally from the agent-security-scanner-mcp npm package.
calllint
Static preflight safety gate for MCP servers — scan configs before you run them. Never executes. Runs locally from the calllint-mcp npm package.
mastyf.ai
Runtime proxy for MCP security, cost governance & audit. Runs locally from the @mastyf_ai/server npm package. Needs 3 environment variables to run.
owasp-agentic-mcp
OWASP Top 10 for AI Agents security assessment tools. Capabilities: full agent security scan, prompt injection detection, tool poisoning check, excessive agency, data leakage. Built by MEOK AI Labs. Runs locally from the owasp-agentic-mcp Python package.
zugawatch
MCP server "zugawatch" as configured in Zuga-luga/zugawatch. Runs locally from the zugawatch Python package.
euvd-mcp
MCP server "euvd-mcp" as configured in TLDart/EUVD-MCP. Runs locally from the euvd-mcp Python package.