Skip to main content
Glama
thisis-najeeb

api-test-mcp

by thisis-najeeb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to api-test-mcp

No user-submitted related servers found.

    Related Servers

    • API Debugger MCP

      MahaR54
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect, test, validate, compare, and debug HTTP APIs through a structured toolkit, with features such as secret redaction, response contract validation, regression comparison, health checks, and incident investigation workflows.
      MIT

    • LockSpec

      LockSpec
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with accurate OpenAPI contract details to prevent hallucinated API calls, supporting multi-version pinning, endpoint discovery, and request validation.
      38 npm
      Apache 2.0
    • fetchsandbox-mcp by fetchsandbox

      fetchsandbox-mcpofficial

      fetchsandbox
      A
      license
      A
      quality
      A
      maintenance
      A deterministic eval engine for coding agents. Your agent claims it fixed the bug—this checks it. The same scenario runs twice against a sandbox of the services your code calls, with failures injected on purpose. It must fail on the old code and pass on the new. The verdict is an exit code, not a model's opinion. Every run leaves a receipt.
      8
      14
      1,014 npm
      1
      MIT

    • openapi-explorer-mcp

      deadrime
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to explore any OpenAPI 3 spec, inspect endpoints and schemas, generate TypeScript types, and make authenticated API calls using credentials mapped to the spec's security schemes.
      7
      478 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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools generally target distinct phases (load, list, call, validate, batch-test, health-check, diff), but call_endpoint/test_endpoint and run_all_tests/check_health both invoke live endpoints and could be confused if the goal is simply 'hit the API'. Descriptions do enough to resolve most ambiguity, so not a 5.

    Naming Consistency5/5

    All tools use lowercase snake_case imperative verbs (load_, list_, call_, validate_, test_, run_, check_, diff_), and each name clearly signals the action. The pattern is highly consistent and predictable.

    Tool Count5/5

    8 tools is well-scoped for an API testing server: loading, exploring, calling, validating, running tests, health-checking, and diffing specs. No redundant or extraneous tools are present.

    Completeness5/5

    The set covers the full workflow from loading an API spec to listing endpoints, making raw calls, validating responses, batch-running endpoint tests, health-checking, and comparing spec versions. Additional tools like auth management or report generation would be optional rather than obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources