interface-audit-mcp
Related Servers
Alternatives to interface-audit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to audit HTML snippets against 18 WCAG 2.2 static checks, look up success criteria and their applicability, retrieve browser-verified failing/corrected markup examples with manual test steps, and resolve ADA Title II, Section 504, and other accessibility deadlines by entity type and date. Runs fully offline with bundled datasets and no API keys, while explicitly reporting that a clean audit is not a conformance claim.4496 npmMIT
- AlicenseAqualityDmaintenanceExposes axe-core accessibility auditing as MCP tools so any MCP-compatible agent can audit HTML for structural and semantic issues.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to audit local PDFs for accessibility issues, batch-audit folders, explain findings, compare reports, and render self-contained HTML, JSON, or Markdown reports without uploading documents or calling models.MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to deterministically audit markup and stylesheets for WCAG contrast failures, accessibility errors and design-token sprawl, and to compute contrast ratios and inventory hardcoded colors, sizes, radii and spacing before shipping UI code. Works across any web stack with Claude Code, Claude Desktop, Codex and Antigravity, and can also run as a CI check that exits non-zero on errors.58 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to check email HTML for delivery-breaking problems before sending, returning structured diagnostics with rule id, severity, line and column, along with a tool that lists every available rule. It runs with no filesystem, network or environment access, so agents can validate markup without gaining new permissions.43 npm6MIT

a11yscopeofficial
FlicenseNot gradedqualityBmaintenanceWCAG 2.2 AA accessibility checks for a URL or for HTML the agent just wrote, run locally in headless Chrome. 31 checks with CSS selectors, snippets and fix guidance; the same engine as the A11yScope Chrome extension.1-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs an audit of HTML content, the other lists the rule catalog. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern: 'audit_html' and 'list_rules'. The naming is clear, predictable, and adheres to a uniform style.
With only two tools, the server is tightly focused on its core functionality of auditing and providing rule information. This count is appropriate and avoids unnecessary bloat.
The server covers the primary audit and rule-listing needs. However, it might benefit from additional tools such as retrieving specific audit results or configuration, but the current set is sufficient for a minimal viable interface-audit server.