F
licenseNot graded
qualityB
maintenanceAnalyzes Git pull request diffs to detect breaking REST and GraphQL API schema changes, providing deterministic AST-level code review and breaking change alerts for CI/CD workflows.
8
-
api-contract-qa
Related Servers
Alternatives to api-contract-qa
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to call real API endpoints and verify responses against OpenAPI specs, supporting contract testing, auth presets, spec diffing, and health checks.854 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables automated semantic analysis of Git pull request diffs to detect breaking REST/GraphQL API schema changes, integrating with MCP-compatible clients for AI-driven code review.-
- AlicenseAqualityDmaintenanceEnables AI clients to validate OpenAPI specs, compare versions, detect breaking changes, and generate changelogs.4MIT
- AlicenseBqualityDmaintenanceEnables natural language exploration of OpenAPI/Swagger specs, allowing users to register APIs, browse endpoints, describe schemas, and detect breaking changes through conversational queries.9230 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to browse, read, compare, and validate OpenAPI contracts for providers and consumers.1MIT
TDQS
A3.6/5.0
Scored across 8 tools
Disambiguation4/5
Each tool has a distinct role in a logical pipeline: list, diff, assess, discover, check live, check deployed, generate, write. The only pair with surface overlap is check_live_conformance vs check_deployed_contract, but the descriptions clearly separate request/response validation from pulling a published contract document, so misselection risk is low.
Naming Consistency5/5
All eight names are snake_case verb_noun (list_operations, diff_contracts, assess_impact, discover_consumer_usage, check_live_conformance, check_deployed_contract, generate_api_tests, write_test). The two check_* tools even form a clean parallel pair.
Tool Count5/5
Eight tools is well within the ideal 3-15 range and each maps to a concrete step in contract QA rather than padding. Generation and file writing are sensibly split rather than merged into one overloaded tool.
Completeness4/5
Coverage spans the full lifecycle: inspect, diff, impact, discover consumers, validate live and deployed, generate and write tests. Minor gaps: discover_consumer_usage only drafts a consumers.yaml entry with no tool to persist or manage entries, and gRPC conformance is explicitly unsupported, but agents can work around both.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues