api-schema-drift-detector

Cloudflare Workers MCP server: api-schema-drift-detector

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
97%
Naming quality
50%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (3)

  • LOWTool 'schema-validator' doesn't follow camelCase/snake_casein schema-validator
  • LOWTool 'drift-detector' doesn't follow camelCase/snake_casein drift-detector
  • LOWTool 'breaking-change-analyzer' doesn't follow camelCase/snake_casein breaking-change-analyzer

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~282Tokens (tool definitions)
~634 BTypical response size
Minimal attention impact (0.22% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "api-schema-drift-detector": {
      "url": "https://api.lazy-mac.com/api-schema-drift-detector/mcp"
    }
  }
}

Remote endpoints

https://api.lazy-mac.com/api-schema-drift-detector/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪schema-validator(schema, data)

Validates if data conforms to a JSON schema. Returns valid:true/false and an error message on failure.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "type": "object",
  "properties": {
    "oldSchema": {
      "type": "object",
      "description": "Previous (deployed) schema version"
    },
    "newSchema": {
      "type": "object",
      "description": "New (candidate) schema version"
    }
  },
  "required": [
    "oldSchema",
    "newSchema"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools
verifiedversion not recorded3 tools