api-schema-drift-detector
Cloudflare Workers MCP server: api-schema-drift-detector
¿Debería usar esto?
Calidad y seguridad
Hallazgos (3)
- LOWTool 'schema-validator' doesn't follow camelCase/snake_caseen schema-validator
- LOWTool 'drift-detector' doesn't follow camelCase/snake_caseen drift-detector
- LOWTool 'breaking-change-analyzer' doesn't follow camelCase/snake_caseen breaking-change-analyzer
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"api-schema-drift-detector": {
"url": "https://api.lazy-mac.com/api-schema-drift-detector/mcp"
}
}
}Puntos de conexión remotos
https://api.lazy-mac.com/api-schema-drift-detector/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (3)
⚪schema-validator(schema, data)
Validates if data conforms to a JSON schema. Returns valid:true/false and an error message on failure.
Esquema de entrada
{
"type": "object",
"properties": {
"schema": {
"type": "object",
"description": "JSON schema to validate against"
},
"data": {
"description": "Data to validate (any type)"
}
},
"required": [
"schema",
"data"
]
}⚪drift-detector(schema, response)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"schema": {
"type": "object",
"description": "Expected JSON schema"
},
"response": {
"type": "object",
"description": "Actual API response to check against schema"
}
},
"required": [
"schema",
"response"
]
}🟡breaking-change-analyzer(oldSchema, newSchema)
Analyzes breaking changes between two schema versions. Detects: field removal, type changes, newly required fields, enum value removal, constraint tightening.
Esquema de entrada
{
"type": "object",
"properties": {
"oldSchema": {
"type": "object",
"description": "Previous (deployed) schema version"
},
"newSchema": {
"type": "object",
"description": "New (candidate) schema version"
}
},
"required": [
"oldSchema",
"newSchema"
]
}Comunidad
Evidencia