Skip to main content
Glama
404Yeti

MCP QA Server

by 404Yeti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP QA Server

No user-submitted related servers found.

    Related Servers

    • Glance

      tariqfernandes4365
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives Claude Code a real browser, enabling it to navigate, click, type, screenshot, and inspect web pages during development. It also supports multi-step JSON test scenarios, assertions, session recording, and visual regression testing against web apps.
      106 npm
      MIT

    • Glance

      Timothy58360
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives Claude Code a real browser, enabling navigation, clicking, form filling, screenshots, and accessibility snapshots directly from the terminal. It also supports multi-step JSON test scenarios, assertions, session recording, and visual regression testing with network and console monitoring.
      106 npm
      MIT

    • Glance

      Dominique45694
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives Claude Code a real browser, letting it navigate pages, click and type, capture inline screenshots, and read accessibility snapshots. It also runs multi-step JSON test scenarios with assertions, visual regression comparison, and network/console monitoring from the terminal.
      106 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: validating config, retrieving reports, listing modules, running specific modules, and running full test suites. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent 'qa_verb_noun' pattern (e.g., qa_check_config, qa_run_tests), making them predictable and easy to understand.

    Tool Count5/5

    Five tools is well-scoped for a QA-focused server, covering essential operations without being excessive or insufficient.

    Completeness5/5

    The tool set covers the core workflow: configuration validation, module listing, selective or full test execution, and report retrieval. No obvious gaps for the given domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources