Mcp Api Change Monitor

com.mambabuiltPublished by mambabuilt.comv1.0.1Updated Nov 7, 2026

API changelog, deprecation, status, OpenAPI, and Sunset header changes since your last run.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Watches third-party API changelogs, status pages, OpenAPI docs and Sunset headers, returning only what changed since the last run.

What you can do
  • Watch vendor presets or any public URL and report new changelog entries, deprecation notices and breaking changes
  • Report new incidents and status changes from status history feeds
  • Compare OpenAPI documents and list operations added, removed or deprecated, plus API version changes
  • Read Sunset and Deprecation response headers from credential-free GET endpoints you list
  • Filter results by keywords or to deprecations and breaking changes only, and keep separate baselines per state key
When to use it
Useful when you need to track API deprecations, breaking changes, incidents or spec drift across vendors such as GitHub, Stripe, OpenAI or Cloudflare, and want a diff against the previous check rather than a full re-read.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. An Apify account and an Apify API token set as APIFY_TOKEN are required for calls; the tool is listed without one. Work runs on Apify, so network access is needed.
Before you install
Calls are billed per event to your Apify account (change rows, source checks, snapshot rows, actor starts); max_charge_usd can cap a run. The APIFY_TOKEN is a secret and should be kept out of shared configs. Listed endpoint URLs are fetched with GET requests, and sources are read by a third-party Apify actor.

Installation

In SourceWeft

  1. Open Mcp Api Change Monitor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

json
{  "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:

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

Source: README.md at commit cd430e3

Tools

1

monitor_api_changes

Monitor API changelogs, deprecations, status, and OpenAPI

Watch third party APIs and return only what changed since the last run with the same state_key. Give vendors (github, stripe, shopify, hubspot, openai, anthropic, google-ads, twilio, slack, notion, atlassian, cloudflare, vercel, plaid), any changelog, feed, deprecation page, status page, or OpenAPI JSON URL in sources, and API endpoints in endpoint_urls. Every source gets one row per run (source_baseline on the first check, then source_check with changes_found), plus one row per change: changelog_entry, deprecation_notice, breaking_change, incident_new, incident_update, incident_resolved, openapi_operation_added, openapi_operation_removed, openapi_operation_deprecated, openapi_version_change, sunset_header, or deprecation_header, each with is_deprecation, is_breaking, and sunset_date. Unreadable sources come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per change row and per source check that is a first check or finds a change; an unchanged source is free.

Parameterswatchsourcesvendorskeywordsstate_keyproxy_modereset_stateendpoint_urlsmax_charge_usdinclude_snapshotmax_changes_per_sourceonly_deprecations_and_breaking

Version history

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Nov 1, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts