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/aditya-ariosity/wcag-accessibility-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/aditya-ariosity/wcag-accessibility-mcp/wcag-accessibility)<a href="https://agentmods.dev/mcp/aditya-ariosity/wcag-accessibility-mcp/wcag-accessibility"><img src="https://agentmods.dev/badge/mcp/aditya-ariosity/wcag-accessibility-mcp/wcag-accessibility/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/aditya-ariosity/wcag-accessibility-mcp/wcag-accessibility"><img src="https://agentmods.dev/badge/mcp/aditya-ariosity/wcag-accessibility-mcp/wcag-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wcag-accessibility 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 12d 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
{
"wcag-accessibility": {
"command": "npx",
"args": [
"-y",
"wcag-accessibility-mcp"
],
"env": {}
}
}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.
- 12d ago First seen · 10 lines scan A 746bd442bd42
wcag-accessibility is an MCP server published in the GitHub repository aditya-ariosity/wcag-accessibility-mcp (1 stars, last pushed 12d 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
Deterministic axe-core accessibility scans (WCAG 2.1 AA, EN 301 549, PDF/UA) via your account. Runs locally from the @wcagc/mcp npm package. Needs 2 environment variables to run.
accessibility-scanner-mcp
Scan any URL for WCAG accessibility issues (axe-core) and get per-element fixes for an AI agent. Runs locally from the accessibility-scanner-mcp npm package. Needs 1 environment variable to run.
a11ychk
A11y Check MCP server — web accessibility scanning (WCAG 2.2 AA + KWCAG 2.2) with Korean remediation guides, for AI coding tools. Runs locally from the @a11ychk/mcp npm package.
mcp
Web accessibility scanning (WCAG 2.2 AA + KWCAG 2.2) with Korean remediation guides. Runs locally from the @a11ychk/mcp npm package.
kilotest
Ensemble testing of web pages for accessibility, usability, and standards conformity. Remote server at kilotest.com.
mcp
Free, real-browser accessibility scanner for AI coding agents. Scans localhost with Playwright + axe-core (and optionally Pa11y/HTMLCS), returns WCAG 2.1 Level A + AA violations with fix plans. Runs locally from the @navable/mcp npm package.