FRENES

Developer tools · MCP server

A11ymcp: MCP server, setup and security

A11ymcp is an open-source MCP server that lets an AI agent test web accessibility and WCAG compliance using axe-core checks. Its repository has 93 stars and its last commit is from March 10, 2026 and it is licensed under MIT.

Score
45/100
Adoption (stars) 20/40
Maintenance 10/30
Framework (licence, registry, official) 15/30
Last commit 8 months ago

What A11ymcp does

According to its repository: “Test URLs and HTML for WCAG 2.0/2.1/2.2 compliance using axe-core, including color contrast, ARIA validation and orientation lock detection.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. A11ymcp is listed under Developer tools, a category of 475 servers in the directory, where it ranks #182 by stars.

Topics declared by the repository: a11y, a11y-testing, accessibility-testing.

Installing and connecting A11ymcp

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to A11ymcp. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on April 25, 2025, the ronantakizawa/a11ymcp repository has 93 stars and 18 forks, with 0 open issues. It has more stars than 65% of the servers in the directory. Last change 8 months ago.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.

StorybookStorybook : 91.4K91.4KFront End ChecklistFront End Checklist : 74.6K74.6KTldrawTldraw : 51.1K51.1KCodebase MemoryCodebase Memory : 47.4K47.4KCCXTCCXT : 44.5K44.5KPostHog MCP ServerPostHog MCP Server : 40.4K40.4KClaude task masterClaude task master : 28.3K28.3KAgent Skills Search ServerAgent Skills Search Server : 26.6K26.6KA11ymcpA11ymcp : 9393
GitHub stars of the most followed servers in the category (log scale); A11ymcp in orange. Checked October 25, 2026.

Verdict

A11ymcp is still a modest project: read its code and compare it with the alternatives before using it.

Strengths

  • Permissive licence (MIT)

Limitations

  • No commit for 8 months
  • Install from source

Frequently asked questions

How do I install A11ymcp?

No package is declared in the MCP registry: clone the ronantakizawa/a11ymcp repository, follow its README, then declare the start command in your client's MCP configuration.

Is A11ymcp free?

The code is published under the MIT licence and can be used free of charge.

Is A11ymcp safe?

No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.

Is it an official server?

Nothing says so: it is a project published by ronantakizawa on GitHub. Check who maintains it before giving it access.

What are the alternatives to A11ymcp?

In the same category: Radar Kubernetes MCP Server, Repowise, Jscpd, and Apify MCP server. Radar Kubernetes MCP Server and Repowise score higher on our grid.

Related articles

Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score