Skip to main content
Glama
Sign In
krds-a11y-mcp

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
      22 npm
      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.
      34
      2,074 PyPI
      3
      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.
      53 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.
      23 npm
      16
      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.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Descriptions actively cross-reference each other to draw boundaries (get_requirements vs get_component for markup, inspect_page vs validate_page for element-level vs page-level checks, list_components vs get_component for index vs detail). The only mild overlap is get_requirements being a subset of get_component's output, but the 'requirements-only for review' framing makes intent clear.

    Naming Consistency5/5

    All nine tools use snake_case verb_object naming (list_components, get_tokens, inspect_page, validate_page, get_page_scaffold, get_framework_guide). The verbs are varied but consistently front-loaded, giving a predictable pattern throughout.

    Tool Count5/5

    Nine tools is well-scoped for a design-system assist server: discovery, detail, requirements, tokens, scaffolding, inspection, validation, and two targeted fix/guide tools. Each tool covers a distinct stage of the build-inspect-validate workflow.

    Completeness4/5

    The surface covers the full lifecycle from scaffolding through component assembly, token lookup, runtime inspection, and accessibility validation, plus framework and icon-bug escape hatches. Minor gaps exist (no explicit pattern enumeration or component search beyond list_components), but agents can work around these.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources