api-diff-monitor

Cloudflare Workers MCP server: api-diff-monitor

Should I use this

Quality & Safety

A
Description quality
93%
Schema completeness
86%
Naming quality
90%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~503Tokens (tool definitions)
~706 BTypical response size
Minimal attention impact (0.39% 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-diff-monitor": {
      "url": "https://api.lazy-mac.com/api-diff-monitor/mcp"
    }
  }
}

Remote endpoints

https://api.lazy-mac.com/api-diff-monitor/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪register_endpoint(name, url, method, headers, body, ...)

Register an API endpoint to monitor for schema changes. Provide name, url, and optionally method/headers/description.

Input Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Identifier for this endpoint"
    },
    "url": {
      "type": "string",
      "description": "API URL to monitor"
    },
    "method": {
      "type": "string",
      "enum": [
        "GET",
        "POST",
        "PUT",
        "PATCH",
        "DELETE"
      ],
      "description": "HTTP method (default: GET)"
    },
    "headers": {
      "type": "object",
      "description": "Request headers"
    },
    "body": {
      "description": "Request body (for POST/PUT)"
    },
    "description": {
      "type": "string",
      "description": "Optional description"
    }
  },
  "required": [
    "name",
    "url"
  ]
}
🟢list_monitored_endpoints

List all registered API endpoints being monitored.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢compare_snapshots(endpoint_id, snapshot_a, snapshot_b, save)

Fetch a registered endpoint and compare against its last snapshot to detect schema changes. Or compare two inline JSON objects directly.

Input Schema

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "type": "string",
      "description": "ID of a registered endpoint to fetch and compare"
    },
    "snapshot_a": {
      "type": "object",
      "description": "Inline \"before\" JSON (omit endpoint_id for direct comparison)"
    },
    "snapshot_b": {
      "type": "object",
      "description": "Inline \"after\" JSON (omit endpoint_id for direct comparison)"
    },
    "save": {
      "type": "boolean",
      "description": "Save snapshot and diff to history (default: true)"
    }
  }
}
🟢get_diff_history(endpoint_id, limit)

Retrieve the schema diff history for a registered endpoint.

Input Schema

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "type": "string",
      "description": "Endpoint ID"
    },
    "limit": {
      "type": "number",
      "description": "Max diffs to return (default: 20, max: 50)"
    }
  },
  "required": [
    "endpoint_id"
  ]
}
🟢detect_breaking_changes(endpoint_id)

Check if a registered endpoint has had any breaking changes (removed fields or type changes).

Input Schema

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "type": "string",
      "description": "Endpoint ID"
    }
  },
  "required": [
    "endpoint_id"
  ]
}
🔴delete_endpoint(endpoint_id)

Remove a monitored endpoint and all its snapshots and diff history.

Input Schema

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "type": "string",
      "description": "Endpoint ID to delete"
    }
  },
  "required": [
    "endpoint_id"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded6 tools