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.
npx agentmods add mcp/aiagentkarl/agent-validator-mcp-server/agent-validator-mcp-servergit clone --depth 1 https://github.com/AiAgentKarl/agent-validator-mcp-serverWrote 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/aiagentkarl/agent-validator-mcp-server/agent-validator-mcp-server)<a href="https://agentmods.dev/mcp/aiagentkarl/agent-validator-mcp-server/agent-validator-mcp-server"><img src="https://agentmods.dev/badge/mcp/aiagentkarl/agent-validator-mcp-server/agent-validator-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-validator-mcp-server 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 5d 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
{ "agent-validator-mcp-server": { "command": "uvx", "args": [ "agent-validator-mcp-server" ] } }
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.
- 5d ago First seen · 8 lines scan A 49c34c8024e5
agent-validator-mcp-server is an MCP server published in the GitHub repository AiAgentKarl/agent-validator-mcp-server (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
mcp-server
BrowserStack's Official MCP Server. Runs locally from the @browserstack/mcp-server npm package. Needs 2 environment variables to run.
agent-audit
Turn Lighthouse audits into coding-agent fix packs for Claude Code, Cursor, and Copilot. Runs locally from the @fullstackdegen/agent-audit npm package.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
pepper
MCP server "pepper" as configured in skwallace36/Pepper. Runs ./tools/pepper-mcp with ./.venv/bin/python3. Needs 1 environment variable to run.
technical-seo
MCP server for technical & on-page SEO audits — crawlability, HTTPS, Core Web Vitals, sitemap, robots.txt, structured data, and AI-crawler access. Reports as Markdown, JSON, or a shareable HTML file. Runs locally from the technical-seo-mcp npm package. Needs 8 environment variables to run.
uxloom
Agent-native UI/UX design validation: journey completeness, state coverage, and WCAG checks. Runs locally from the uxloom npm package. Needs 1 environment variable to run.