Skip to content

io.github.lazymac2x/api-schema-drift-detector

by lazymac2x · remote · no sign-in to list tools · v1.0.0 · published by GitHub user lazymac2x

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

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http api-schema-drift-detector https://api.lazy-mac.com/api-schema-drift-detector/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • drift-detectorDetects differences between an actual API response and an expected JSON schema.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote 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.
Only reads 2Claude Code: allow
  • breaking-change-analyzerAnalyzes breaking changes between two schema versions.No findings

    Why it is in this group

    • The description's first verb is "analyze": a word for reading.
    Description, as the server wrote it
    Analyzes breaking changes between two schema versions. Detects: field removal, type changes, newly required fields, enum value removal, constraint tightening.
  • schema-validatorValidates if data conforms to a JSON schema.No findings

    Why it is in this group

    • The description's first verb is "validate": a word for reading.
    Description, as the server wrote it
    Validates if data conforms to a JSON schema. Returns valid:true/false and an error message on failure.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http api-schema-drift-detector https://api.lazy-mac.com/api-schema-drift-detector/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__api-schema-drift-detector__schema-validator",
      "mcp__api-schema-drift-detector__breaking-change-analyzer"
    ],
    "ask": [
      "mcp__api-schema-drift-detector__drift-detector"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as api-schema-drift-detector. Review it before you use it.