Skip to main content
Glama
n2400813g

blop

by n2400813g
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to blop

No user-submitted related servers found.

    Related Servers

    • loopcheck

      WeiR-h
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI builders to approve requirements, replay browser checks, and return regression evidence through MCP, supporting acceptance testing without code modification.
      MIT

    • playwright-fixer-mcp

      BobChochola
      F
      license
      A
      quality
      D
      maintenance
      Automated Playwright E2E test repair powered by a self-improving, governed MCP server that runs failing tests, collects failure artifacts, reasons about root causes, validates and applies fixes, and re-runs to verify.
      12
      -
    • AgentsGate by agentsgate

      AgentsGateofficial

      agentsgate
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to securely call MCP tools with risk scoring, checkpoints, rollback, and approval workflows.
      1 npm
      MIT

    • chrome-workflows

      XamuAvila
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for storing and managing QA workflows, encrypted credentials, and browser test run history. Enables agents to create targets, workflows, and retrieve decrypted credential bundles for test execution.
      -
    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

    B3.3/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes, but there is some overlap between record_test_flow and evaluate_web_task (both use a browser agent) and between save_auth_profile and capture_auth_session (both deal with auth profiles). The descriptions help clarify, but a few tools could still be confused.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., record_test_flow, run_release_check, get_release_context). Even longer names like package_authenticated_saas_baseline maintain the convention, making the set predictable.

    Tool Count2/5

    With 28 tools, the server exceeds the 25+ threshold for 'too many' per the calibration. While the broad QA/release scope justifies some density, the count feels heavy and could overwhelm agents without a clear need for this many distinct operations.

    Completeness4/5

    The tool surface covers the core QA workflow well: recording flows, running releases, getting results, debugging, and gaining insights. Minor gaps exist, such as no explicit update/delete for flows or auth profiles and no direct list of all flows, but these are workable via existing tools.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources