Skip to main content
Glama
accessibility-mcp-demo

accessibility-mcp-demo

by KWADMOD

Related Servers

Alternatives to accessibility-mcp-demo

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to analyze public websites, follow progress, retrieve shareable reports, compare multiple URLs, list checks and recent activity, and surface fixes ranked by impact.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables rendering and auditing live web pages or pasted HTML markup for WCAG 2.1/2.2 violations, returning scores, findings, and shareable report links. Also lets you fetch previously stored scan reports by id and list every WCAG criterion the scanner can emit.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude and other agents to capture web page screenshots and PDFs, compare two pages with a visual diff, and run WCAG accessibility audits. Captured images are returned inline so a model can inspect the page it just requested within a single turn.
      5
      102 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Connects Claude to a live Chrome browser's accessibility tree to generate stable, framework-agnostic test selectors and perform accessibility audits. It enables users to read element roles and states exactly as a screen reader would to help write, debug, and migrate test suites using natural language.
      8
      4 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to retrieve cited European Accessibility Act obligations per jurisdiction, compare requirements, generate conformance statements, and explain EN 301 549 criteria. It also scans URLs or HTML with axe-core and maps accessibility findings to the relevant EN 301 549 clauses.
      MIT

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: list_scan_targets is a discovery/introspection call, while scan_page performs the actual accessibility scan. Descriptions explicitly state when to use each and even tell the agent it rarely needs list_scan_targets, leaving no room for misselection.

    Naming Consistency5/5

    Both names follow the same snake_case verb_noun convention (list_scan_targets, scan_page) and the verb choice matches the action type (list for enumeration, scan for the operation). No mixing of styles or vague verbs.

    Tool Count3/5

    Two tools is thin even for a demo server; list_scan_targets is self-described as rarely needed, effectively leaving a single actionable tool. The scope is narrow enough that this is defensible, but the surface feels minimal rather than well-scoped.

    Completeness4/5

    For the stated purpose of checking one public page for accessibility issues, the surface covers the core operation, and the descriptions set honest expectations about limits. Minor gaps exist (no multi-page/batch scanning, no way to re-fetch a past report since the service keeps no records), but these are workarounds an agent can live with.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues