Skip to main content
Glama
kim-dongho

krds-a11y-mcp

by kim-dongho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to krds-a11y-mcp

No user-submitted related servers found.

    Related Servers

    • swwa-mcp

      SWJoong
      A
      license
      A
      quality
      A
      maintenance
      Enables automated web accessibility checking and review against Korea's KWCAG 2.2 standard, supporting static HTML/contrast validation, live URL audits, and certification readiness estimation.
      7
      4 npm
      MIT

    • accessibility-mcp-server

      AiAgentKarl
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to perform comprehensive web accessibility checks (WCAG 2.1/2.2) including color contrast analysis, ARIA validation, and full accessibility report generation without requiring any API key.
      8
      23 PyPI
      MIT

    • a11y-toolkit

      kinti
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to perform WCAG 2.2 accessibility audits, including contrast ratio checks for color pairs and text-over-image, generate EU legal accessibility declarations, and produce aria-live monitoring snippets, all through local, multilingual tools.
      26
      1,023 PyPI
      2
      MIT

    • mcp-a11y-tools

      rog0x
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with web accessibility analysis tools via MCP, enabling checks for alt text, heading hierarchy, color contrast, ARIA validation, and form accessibility.
      32 npm
      MIT

    • KRDS MCP Server

      KRDS-MCP
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides Korean government design system (KRDS) guidelines to AI models via MCP, enabling AI assistants to comply with KRDS standards when developing government websites and digital services.
      12 npm
      15
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct part of the a11y workflow (tokens, component index, component detail, scaffold, validation, style inspection). The only real overlap is get_component vs get_requirements, which both surface accessibility requirements; the descriptions do clarify that get_requirements omits markup for review, but an agent could still misselect between them.

    Naming Consistency5/5

    All names follow a clean snake_case verb_noun pattern (get_tokens, list_components, get_component, get_page_scaffold, validate_page, inspect_page). No camelCase mixing or vague verbs; the convention is predictable throughout.

    Tool Count5/5

    Nine tools is well-scoped for an accessibility toolkit spanning discovery, scaffolding, requirement lookup, validation, and debugging. Each tool earns its place without redundancy or bloat.

    Completeness4/5

    The surface covers a full a11y lifecycle: token lookup, component discovery/detail, scaffolds, requirement review, browser validation, and computed-style inspection, plus framework and icon-fix guides. Minor gap in that there are no authoring/update operations, but the server is clearly read/query/generate oriented, so coverage is largely sufficient.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources