Api Schema Drift Detector
Wire MCP tools that detect API schema drift so your agent catches contract breaks before users or integrators do.
Overview
io.github.lazymac2x/api-schema-drift-detector is a MCP server for the Ship phase that offers hosted tools to detect API schema drift via streamable HTTP.
What is this MCP server?
- Remote MCP at https://api.lazy-mac.com/api-schema-drift-detector/mcp (streamable-http)
- io.github.lazymac2x/api-schema-drift-detector version 1.0.0 on Cloudflare Workers
- Agent-accessible drift detection for evolving API surfaces
- Supports solo builders maintaining public or partner-facing API contracts
- Open GitHub repo lazymac2x/api-schema-drift-detector-api
- Single streamable-http remote URL
- Server name matches catalog id io.github.lazymac2x/api-schema-drift-detector
What problem does it solve?
Small teams ship API tweaks without noticing response shape changes until client apps break or integration tests fail late.
Who is it for?
API-first indie products with external consumers who need consistent JSON contracts through frequent deploys.
Skip if: Internal-only scripts with no published schema or teams already running dedicated contract-testing CI that does not use MCP.
What do I get? / Deliverables
After MCP registration, your agent can run drift-oriented tooling against your documented schema versus live behavior before you ship releases.
- MCP-connected schema drift detection workflow
- Earlier visibility into breaking response changes
- Safer API releases for downstream clients and integrators
Recommended MCP Servers
Journey fit
Schema drift detection is a gate in Ship when you validate contracts against docs, clients, and deployed workers. Testing covers contract and regression checks, including whether live responses still match declared OpenAPI or JSON shapes.
How it compares
MCP contract-drift helper, not a full OpenAPI design studio or generic JSON schema editor skill.
Common Questions / FAQ
Who is api-schema-drift-detector for?
Solo builders and small API teams using MCP agents who want schema drift checks integrated into Ship-phase testing conversations.
When should I use api-schema-drift-detector?
Use it before releases when you change handlers, serializers, or worker bindings and must confirm responses still match your contract.
How do I add api-schema-drift-detector to my agent?
Point your MCP client at https://api.lazy-mac.com/api-schema-drift-detector/mcp with type streamable-http, save config, and reload tools.