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/ICJIA/axecap-mcpWrote 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/icjia/axecap-mcp/axecap)<a href="https://agentmods.dev/mcp/icjia/axecap-mcp/axecap"><img src="https://agentmods.dev/badge/mcp/icjia/axecap-mcp/axecap.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
axecap 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
{ "axecap": { "command": "npx", "args": [ "-y", "@icjia/axecap" ] } }
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 · 9 lines scan A 08e319412479
axecap is an MCP server published in the GitHub repository ICJIA/axecap-mcp (0 stars, last pushed 24d 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
pattern-mcp
MCP tool that judges whether a UI component need should be met with an existing shadcn/ui, 21st.dev, or ReUI component or requires a custom build, using field/requirement coverage scored against real component code. Runs locally from the pattern-mcp npm package.
agentvision
Eyes for AI Agents — a machine-graded visual feedback loop coding agents consume to self-correct before claiming done. Runs locally from the agentvision Python package.
gridproof
Gridproof your UI — automated spacing & grid QA in the agent loop (MCP server). Runs locally from the gridproof npm package.
one-shot-ui
Deterministic UI extraction and screenshot diffing for AI coding agents. Runs locally from the one-shot-ui npm package.
slop-eval
Scores AI-generated UI for genericness ("slop") using an Anthropic LLM-judge rubric, with a --json mode for CI/agent quality gates and a documented programmatic API (scorecomposite, ScoreInput, LLMJudgeSource) for in-process use by agent frameworks. Runs locally from the slop-eval-cli Python package.
chart-color-audit
CI-friendly accessibility audit for chart color palettes: WCAG contrast, CVD simulation, OKLab ΔE. Runs locally from the chart-color-audit npm package.