io.github.lazymac2x/api-schema-drift-detector is an MCP server published by io.github.lazymac2x, hosted at api.lazy-mac.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 3 tools, including schema-validator, drift-detector, breaking-change-analyzer.
Cloudflare Workers MCP server: api-schema-drift-detector
160 connections through 5 shared values. Tap any node.
Validates if data conforms to a JSON schema. Returns valid:true/false and an error message on failure.
| Parameter | Type | Description |
|---|---|---|
| data * | any | Data to validate (any type) |
| schema * | object | JSON schema to validate against |
{
"name": "schema-validator",
"description": "Validates if data conforms to a JSON schema. Returns valid:true/false and an error message on failure.",
"inputSchema": {
"type": "object",
"required": [
"schema",
"data"
],
"properties": {
"data": {
"description": "Data to validate (any type)"
},
"schema": {
"type": "object",
"description": "JSON schema to validate against"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Detects differences between an actual API response and an expected JSON schema. Reports missing_required (error), type_mismatch (error), enum_violation (error), missing_optional (warning), unexpected_field (info). Recurses into nested objects.
| Parameter | Type | Description |
|---|---|---|
| schema * | object | Expected JSON schema |
| response * | object | Actual API response to check against schema |
{
"name": "drift-detector",
"description": "Detects differences between an actual API response and an expected JSON schema. Reports missing_required (error), type_mismatch (error), enum_violation (error), missing_optional (warning), unexpected_field (info). Recurses into nested objects.",
"inputSchema": {
"type": "object",
"required": [
"schema",
"response"
],
"properties": {
"schema": {
"type": "object",
"description": "Expected JSON schema"
},
"response": {
"type": "object",
"description": "Actual API response to check against schema"
}
}
}
}Analyzes breaking changes between two schema versions. Detects: field removal, type changes, newly required fields, enum value removal, constraint tightening.
| Parameter | Type | Description |
|---|---|---|
| newSchema * | object | New (candidate) schema version |
| oldSchema * | object | Previous (deployed) schema version |
{
"name": "breaking-change-analyzer",
"description": "Analyzes breaking changes between two schema versions. Detects: field removal, type changes, newly required fields, enum value removal, constraint tightening.",
"inputSchema": {
"type": "object",
"required": [
"oldSchema",
"newSchema"
],
"properties": {
"newSchema": {
"type": "object",
"description": "New (candidate) schema version"
},
"oldSchema": {
"type": "object",
"description": "Previous (deployed) schema version"
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.