Skip to main content
Glama
Mr-Lucasz

Conversational API Test MCP

by Mr-Lucasz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Conversational API Test MCP

No user-submitted related servers found.

    Related Servers

    • api-test-mcp

      thisis-najeeb
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to call real API endpoints and verify responses against OpenAPI specs, supporting contract testing, auth presets, spec diffing, and health checks.
      8
      29 npm
      MIT
    • fetchsandbox-mcp by fetchsandbox

      fetchsandbox-mcpofficial

      fetchsandbox
      A
      license
      A
      quality
      B
      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.
      19
      188 npm
      1
      MIT

    • horus

      xucailiang
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent-planned, human-reviewed HTTP API testing through MCP, turning OpenAPI/Swagger definitions and requirements into executable Hurl/k6 test plans. Supports plan review, execution, cleanup, and reports for coding agents such as Codex and Claude Code.
      MIT

    • 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

    • Swagger/Postman MCP Server

      MCP-Mirror
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to dynamically discover and interact with APIs through Swagger/OpenAPI specifications and Postman collections using a strategic four-tool approach. It streamlines API integration by providing universal tools for endpoint discovery, detailed request information, and authenticated execution.
      1
      -

    • FuzzSpec

      hanifalkauni
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding assistants to inspect OpenAPI specs, fuzz live REST endpoints with boundary and adversarial vectors, replay failing anomalies deterministically without AI tokens, and scaffold OpenAPI specs from source routes.
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target distinct actions (list vs read vs summarize, plan vs run VANDER checks, single request vs flow vs eval). A few pairs overlap in purpose—read_api_definition vs summarize_api_definition, convert_legacy_to_canonical vs import_curl—but descriptions provide clear guidance on when to use each.

    Naming Consistency4/5

    Nearly all names follow a snake_case verb_noun pattern (execute_api_request, plan_vander_checks, set_environment_variable). Minor deviations such as set_environment vs set_environment_variable and the whimsical summon_vander keep it from being perfectly uniform, but the convention is still predictable.

    Tool Count3/5

    21 tools is heavy for the domain; the server covers definition management, legacy conversion, execution, evals, VANDER checks, environment handling, and workspace init. Several pairs could arguably be merged (read/summarize, plan/run VANDER), making the count borderline rather than well-scoped.

    Completeness4/5

    The surface covers create/read/update via upsert, list, summarize, legacy conversion, request execution, assertions, flows, evals, VANDER checks, environment variables, and workspace init. A notable gap is an explicit delete tool for definitions or endpoints; upsert with replace_file can overwrite but does not obviously delete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources