Skip to main content
Glama
dolrea77

inspection-mcp

by dolrea77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to inspection-mcp

No user-submitted related servers found.

    Related Servers

    • Limetest MCP Server

      m2rads
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables automated end-to-end testing powered by Playwright where test cases are defined in natural language and executed by AI. Uses lightweight snapshot analysis with vision mode fallback for sophisticated testing scenarios.
      3
      Apache 2.0

    • tuxedo-qa

      jonathan-ponciano
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to create, run, autocorrect, and monitor Playwright tests for your app with a local dashboard, credential vault, and public status page.
      16
      MIT

    • AutoDev MCP

      rookiejefren
      F
      license
      Not graded
      quality
      D
      maintenance
      A dual-track testing server that combines CLI test execution with Playwright-based browser testing and persistent SQLite logging. It enables automated test pipelines, Git integration, and evidence-based requirement generation to streamline the development lifecycle.
      -
    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.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct operation in the QA workflow: registration, preparation, script saving, listing, template retrieval, update, delete, bulk run, and single run. The only potential overlap is between run_qa and run_qa_single, but their descriptions clearly distinguish bulk vs. single execution.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (register_, prepare_, save_, list_, get_, update_, delete_, run_). The shared 'run_qa' prefix for bulk and single execution is a minor but acceptable deviation.

    Tool Count5/5

    Nine tools cover the full QA lifecycle without redundancy. Each tool addresses a distinct step, from Excel registration to script debugging, and none feel extraneous.

    Completeness4/5

    The toolset covers the complete workflow: import, prepare, script, run, update, and delete. Minor gaps include a dedicated 'get_qa_script' to retrieve saved script contents and no historical run result retrieval, but these can be worked around via existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources