Skip to main content
Glama
Mhdd-24

API Contract MCP

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to API Contract MCP

No user-submitted related servers found.

    Related Servers

    • api-testing-agent

      SHREELASYABEZAWADA
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to discover API endpoints from OpenAPI/Swagger specs, send HTTP requests, validate responses, and analyze status codes for automated API testing.
      1
      -

    • 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.
      42 npm
      Apache 2.0

    • 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

    • Tiltmeter

      tiltmeter-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to check whether third-party API responses have drifted, inspect expected schemas, review change history, list monitored endpoints, and trigger checks before agents trust an API.
      1,087 PyPI
      MIT
    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

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: health check, response validation, and endpoint listing. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share a consistent 'apicontract_' prefix and use lowercase names. There is minor inconsistency between nouns ('status', 'endpoints') and verbs ('validate'), but the pattern is still predictable.

    Tool Count4/5

    Three tools is on the smaller side but appropriate for a focused API contract utility. Each tool serves a clear, non-redundant function, and the count does not feel artificially inflated or overly thin.

    Completeness3/5

    The tool set covers core health check, validation, and endpoint discovery, but lacks broader contract lifecycle operations like importing, diffing, or managing multiple contracts. Agents can perform basic tasks but may need external tooling for full contract workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources