mcpField
M
mcp-api-change-monitor

mcp-api-change-monitor

Local
github.com/mambalabsdevDeveloper Tools0Updated 1w ago

About mcp-api-change-monitor

mcp-api-change-monitor checks API vendors and public URLs for changes since the previous run. It is for teams tracking deprecations, breaking changes, status incidents, OpenAPI operations, and response headers; Apify performs the checks while the package returns dataset rows.

Key features

  1. 01Track changelog and deprecation updates
  2. 02Detect status incident changes
  3. 03Compare published OpenAPI operations
  4. 04Read Sunset and Deprecation headers
  5. 05Keep per-source comparison state

Use cases

  1. 01Monitor vendor API deprecations
  2. 02Watch OpenAPI documents for removed operations
  3. 03Check status pages for new incidents
  4. 04Track headers on unauthenticated API endpoints

MCP support

The MCP server exposes one tool, monitor_api_changes, which starts the Apify actor, waits for completion, and returns its dataset rows.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-mambabuilt-mcp-api-change-monitor": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-api-change-monitor"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}
Run commandnpx -y @mambalabsdev/mcp-api-change-monitor
Environment variables to set
APIFY_TOKENSecretApify API token from https://console.apify.com/account/integrations

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@mambalabsdev/mcp-api-change-monitor1.0.1

Tools

1

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
watcharrayNoFor vendor presets, any of: changelog, deprecations, status, headers, openapi. Empty means changelog, deprecations, status, and headers. openapi reads the vendor's OpenAPI document (up to 14 MB) and reports operations added, removed, or deprecated. Without changelog, changelog sources return only deprecations and breaking changes. URLs you list in Source URLs are always read.
sourcesarrayNoAny other public URLs to watch, one per line: a changelog or release notes page, an RSS or Atom feed, a deprecation or sunset dates page, a Statuspage site or its history.rss feed, or an OpenAPI or Swagger JSON document. The kind is detected from what the URL returns.
vendorsarrayNoAPI vendors to watch, one per line. Each expands to the public sources read for it: changelog, deprecation page, status history, and OpenAPI document where one is published. Available: github, stripe, shopify, hubspot, openai, anthropic, google-ads, twilio, slack, notion, atlassian, cloudflare, vercel, plaid.
keywordsarrayNoReturn only change rows whose title, summary, categories, or operation contains one of these words. Every change still updates the saved state.
state_keystringNoNames the saved state, so separate schedules keep separate baselines. Runs with the same state key and source compare against each other.
proxy_modeenumNoHow sources are fetched. Default auto.auto | direct
reset_statestringNotrue to ignore the saved state and record a new baseline for every source. Default false.
endpoint_urlsarrayNoAPI endpoints to call without credentials, one per line. The response headers are read for Sunset (RFC 8594), Deprecation (RFC 9745), and Link relations deprecation, sunset, and successor-version. Only GET requests are sent.
max_charge_usdstringNoOptional. The run stops before it would charge more than this.
include_snapshotstringNotrue to also return the current entries, incidents, or operations of a source on its first check, up to Max change rows per source. Each snapshot row is billed as a snapshot row. Default false.
max_changes_per_sourcestringNoChange rows returned per source per run, 1 to 1000. The rest are counted in changes_found. Default 100.
only_deprecations_and_breakingstringNotrue to return only change rows tagged as a deprecation or breaking change, OpenAPI operations removed or deprecated, and header changes. Incidents and plain changelog entries are left out. Default false.

Details

From the project README

API Change Monitor MCP Server

Glama score MCP Registry npm version npm downloads license mcpservers.org

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

  • 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

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.

InputTypeDescription
vendorsarrayAPI vendors to watch, one per line. Each expands to the public sources read for it: changelog, deprecation page, status history, and OpenAPI document where one is published. Available: github, stripe, shopify, hubspot, openai, anthropic, google-ads, twilio, slack, notion, atlassian, cloudflare, vercel, plaid
sourcesarrayAny other public URLs to watch, one per line: a changelog or release notes page, an RSS or Atom feed, a deprecation or sunset dates page, a Statuspage site or its history.rss feed, or an OpenAPI or Swagger JSON document. The kind is detected from what the URL returns
endpoint_urlsarrayAPI endpoints to call without credentials, one per line. The response headers are read for Sunset (RFC 8594), Deprecation (RFC 9745), and Link relations deprecation, sunset, and successor-version. Only GET requests are sent
watcharrayFor vendor presets, any of: changelog, deprecations, status, headers, openapi. Empty means changelog, deprecations, status, and headers. openapi reads the vendor's OpenAPI document (up to 14 MB) and reports operations added, removed, or deprecated. Without changelog, changelog sources return only deprecations and breaking changes. URLs you list in Source URLs are always read
keywordsarrayReturn only change rows whose title, summary, categories, or operation contains one of these words. Every change still updates the saved state
only_deprecations_and_breakingstringtrue to return only change rows tagged as a deprecation or breaking change, OpenAPI operations removed or deprecated, and header changes. Incidents and plain changelog entries are left out Default false
max_changes_per_sourcestringChange rows returned per source per run, 1 to 1000. The rest are counted in changes_found Default 100
include_snapshotstringtrue to also return the current entries, incidents, or operations of a source on its first check, up to Max change rows per source. Each snapshot row is billed as a snapshot row Default false
state_keystringNames the saved state, so separate schedules keep separate baselines. Runs with the same state key and source compare against each other
reset_statestringtrue to ignore the saved state and record a new baseline for every source Default false
max_charge_usdstringOptional. The run stops before it would charge more than this
proxy_modestringHow sources are fetched Default auto

Pricing

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

EventFree planBronzeSilverGold
change-row, one change on a watched source since the last run: a new changelog entry, deprecation notice, or breaking change, a new or updated status incident, an OpenAPI operation added, removed, or deprecated, an API version change, or a Sunset or Deprecation header change$0.0035$0.003325$0.00315$0.002975
source-check, one source read and compared with its saved state: the first check of a source, which records the baseline, or a later check that finds at least one change. A source where nothing moved returns a free no_change row, and a source that cannot be read is free$0.003$0.00285$0.0027$0.00255
snapshot-row, one current entry, incident, or operation on the first check of a source, returned only when include_snapshot is on$0.001$0.00095$0.0009$0.00085
apify-actor-start, per run start$0.001$0.001$0.001$0.001

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.