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/dl-eigenart/agentshield-platformWrote 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/dl-eigenart/agentshield-platform/agentshield-mcp-agentshield-mcp)<a href="https://agentmods.dev/mcp/dl-eigenart/agentshield-platform/agentshield-mcp-agentshield-mcp"><img src="https://agentmods.dev/badge/mcp/dl-eigenart/agentshield-platform/agentshield-mcp-agentshield-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agentshield-mcp 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
{
"agentshield-mcp": {
"command": "npx",
"args": [
"-y",
"@eigenart/agentshield-mcp"
],
"env": {
"AGENTSHIELD_API_KEY": ""
}
}
}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 · 12 lines scan A e103ca4c80b1
agentshield-mcp is an MCP server published in the GitHub repository dl-eigenart/agentshield-platform (0 stars, last pushed 3mo 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
mcpsafetywarden
MCP proxy server with behavioral profiling, security scanning, risk gating, and safe execution. Runs locally from the mcpsafetywarden Python package.
plantuml
MCP server for generating PlantUML diagrams. Runs locally from the plantuml-mcp-server npm package. Needs 1 environment variable to run.
zugashield
AI Agent Security System - 7-layer defense against prompt injection, data exfiltration, and AI-specific attacks. Runs locally from the zugashield Python package.
kernel
Open proof-required execution kernel for consequential actions. Runs locally from the actenon-kernel Python package.
vitna-compliance-preflight
Pre-action allow/deny for AI agents. 24 statutes, 13 jurisdictions: EU AI Act, GDPR, DPDP. Runs locally from the @costrinity/vitna-compliance-mcp npm package. Needs 4 environment variables to run.
shield
MCP server "shield" as configured in kobepaw/goop-shield-community. Launched with goop-shield mcp --port 8787.