Api Change Monitor MCP Server

API Change Monitor MCP Server

An MCP server for the Mamba Labs API Deprecation and Breaking Change Monitor actor on Apify. Give it API vendors or URLs. Each run compares every source with the state saved by the last run and returns only what changed.

What's Inside

• What it does
• Quick start
• Prerequisites
• Example prompts
• Tool
• Inputs
• Pricing
• Your keys
• Full actor documentation
• License

What it does

• Changelogs: new entries from the vendor's changelog feed or page, tagged deprecation_notice or breaking_change when the wording says so, with the first sunset_date named.
• Status: new incidents and status changes from the vendor's status history feed.
• OpenAPI: operations added, removed, or deprecated, and the API version, from a published OpenAPI JSON document.
• Headers: Sunset and Deprecation response headers on API endpoints you list.
• One row per source per run: source_baseline on the first check under a state_key, then source_check with changes_found, or a free no_change row when nothing moved.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-api-change-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-api-change-monitor"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The monitor_api_changes tool appears.

Prerequisites

• Node.js 18 or newer.
• An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.

Example prompts

• "Did GitHub or OpenAI announce any deprecations or breaking changes since last week?"
• "Watch the Stripe and GitHub OpenAPI documents and tell me which operations were removed or deprecated."
• "Has any incident been opened on the Cloudflare or Vercel status pages since yesterday?"

Tool

monitor_api_changes. One tool. Example arguments:

{
  "vendors": [
    "github",
    "openai"
  ],
  "state_key": "api-watch-daily"
}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults. Numbers and booleans are sent as strings.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

A source where nothing moved returns a free no_change row, sources that cannot be read are free, and so is the one row a refused input returns.

Your keys

The actor needs no key. It reads public changelogs, feeds, status history, and OpenAPI documents, and calls the endpoints you list without credentials. It holds no key of any kind. Proxy traffic adds nothing to your price: Mamba Labs pays the platform costs of the run.

Full actor documentation

apify.com/mambalabs/api-change-monitor

License

MIT. See LICENSE.