API Change Feed

dev.changefeedPublished by changefeed.devOfficial publisherv0.3.1Updated Nov 6, 2026

What broke since your version, for 60 popular APIs/SDKs. Free quick check; full reports via x402.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Remote MCP server that tells an assistant what broke, was deprecated or fixed in 60 popular APIs and SDKs since a given version.

What you can do
  • List the 60 tracked APIs/SDKs and the package names to query them by
  • Preview the latest breaking, deprecation and security headlines across all sources to check freshness
  • Run a free quick check on whether a library changed since the version your code targets, with a verdict, major versions crossed and counts of breaking changes, deprecations and security fixes
  • Get a paid upgrade report for one package since a target version, with the sentence that triggered each label
  • Fetch normalized change records for one or all tracked sources, filterable by date and kind
  • Get a paid digest of everything breaking, deprecated or security-related across all sources since a date, grouped by source
When to use it
Useful when an assistant writes or upgrades code against libraries it may only know from older training data and needs to confirm what changed. It suits coding agents that want a quick free sanity check before generating code, or a detailed per-package upgrade report.
Requirements
Runs as a remote streamable HTTP endpoint; no account or API key is needed. Paid tools require per-call payment in USDC on Base via x402, so a wallet able to pay is needed for upgrade_check, get_changes and digest. Network access to the endpoint is required.
Before you install
Three tools cost money per call: upgrade_check at $0.01, get_changes at $0.005 and digest at $0.02, paid in USDC on Base via x402, so calls spend funds from a wallet. The free tools only cover a limited preview and quick check. Coverage is limited to the 60 tracked sources, and change labels are derived from release notes, so verify critical findings before relying on them.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.changefeed%2Fapi-change-feed/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "api-change-feed": {
      "type": "http",
      "url": "https://changefeed.dev/mcp"
    }
  }
}

Tools

6

list_sources

List the 60 APIs/SDKs we track and the package names to query them by. Free.

Takes no parameters.

preview_changes

Latest five breaking/deprecation/security headlines across all sources, to check freshness. Free.

Takes no parameters.

quick_check

Free. Before writing code against a library you may know only from older training data, check whether it changed since that version: verdict, major versions crossed, how many breaking changes, deprecations and security fixes, and the top three breaking headlines. Call upgrade_check (paid) for the full details with evidence.

Parametersfromrequiredpackagerequired

upgrade_check

What changed in a package since the version your code targets: breaking changes, deprecations, security fixes and major versions crossed, with the sentence that triggered each label. Call this before writing code against a library you may know only from older training data. Costs $0.01 (x402, USDC).

Parametersfromrequiredpackagerequired

get_changes

Normalized change records (breaking, deprecation, security, release) for one tracked API/SDK or all of them, filterable by date and kind. Costs $0.005 (x402, USDC).

Parameterskindslimitsincesource

digest

Everything breaking, deprecated or security-related across all tracked sources since a date, grouped by source. Costs $0.02 (x402, USDC).

Parameterskindssince

Version history

1
  1. v0.3.1LatestNov 6, 2026

Score

83% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.