Skip to main content
Glama

Related Servers

Alternatives to pour

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Audits web pages for WCAG 2.2 AA accessibility aligned with the GOV.UK standard using axe-core and headless Chromium, returning structured JSON, markdown reports, and GDS compliance summaries.
      4
      41
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables auditing a local PDF against machine-checkable PDF/UA accessibility basics and returns an actionable JSON report with checks, failures, route, and verdict, entirely offline without uploading the document.
      324 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets developers and MCP agents run deterministic local HTML audits, turning inline HTML into structured findings for missing labels, unnamed buttons, skipped headings, ambiguous links, duplicate IDs, and missing landmarks. It also exposes a rule list and returns stable, actionable reports without external API keys.
      2
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      WCAG 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
      -
    • A
      license
      A
      quality
      B
      maintenance
      Checks a website or local dev server with axe-core (WCAG 2.0/2.1 A and AA) and returns a fix prompt with real examples from the pages, for the AI tool to fix the source. Automated checks find roughly a third of accessibility problems.
      1
      153 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools target clearly different outputs: a WCAG rule audit, a keyboard tab-order walk, and a rendered PNG. The one soft overlap is that pour_screenshot exposes a 'focusOrder' lens while pour_focus_order returns structured tab-order data, and landmarkMap has no dedicated tool, so an agent may occasionally hesitate over which to reach for.

    Naming Consistency5/5

    All three names share the pour_ prefix and snake_case, with a stable noun/action describing the artifact produced (audit, focus_order, screenshot). No mixed conventions or vague verbs.

    Tool Count4/5

    Three tools is compact but each maps to a genuinely distinct inspection mode of an accessibility engine, and the huge simulation list lives inside one parameter rather than being split into dozens of tools. Slightly thin for the breadth of the domain, but well scoped rather than padded.

    Completeness4/5

    The surface covers the core workflow: rule-based auditing, keyboard reachability/order, and visual simulation rendering. Minor gaps exist around structured landmark/heading output (only available as a screenshot lens) and no way to exercise interactive states beyond page-load parameters, but nothing that blocks typical agent use.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues