# API Change Feed (remote · changefeed.dev)

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

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `changefeed.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-changefeed-api-change-feed/changefeed.md), [page](https://verifymcp.io/servers/dev-changefeed-api-change-feed/changefeed)

## Channel facts

- Endpoint: `https://changefeed.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 706 tokens (~117/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the API Change Feed MCP server?

API Change Feed is a hosted endpoint at https://changefeed.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-changefeed-api-change-feed 'https://changefeed.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-changefeed-api-change-feed": {
      "url": "https://changefeed.dev/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.dev-changefeed-api-change-feed]
url = "https://changefeed.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-changefeed-api-change-feed": {
      "type": "remote",
      "url": "https://changefeed.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-changefeed-api-change-feed --url 'https://changefeed.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-changefeed-api-change-feed:
    url: "https://changefeed.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-changefeed-api-change-feed": {
      "Transport": "http",
      "Url": "https://changefeed.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-changefeed-api-change-feed -t streamable-http -u 'https://changefeed.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 65, +1)

- [security] Tool “upgrade_check” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail

### 2026-11-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 62, +1)

- [security] Tool “list_sources” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 93 → 115
- [functional improvement] Tool coverage: 80% → 100%
- [cosmetic] “digest” reworded the description of “kinds”
- [cosmetic] “get_changes” reworded the description of “limit”
- [cosmetic] “get_changes” reworded the description of “since”
- [cosmetic] “get_changes” reworded the description of “source”
- [cosmetic] “quick_check” reworded the description of “package”
- [cosmetic] “upgrade_check” reworded the description of “package”

### 2026-11-11 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `list_sources` (~40 tokens)

List the 60 APIs/SDKs we track, each one's ecosystem (npm or pypi) and the package names to query them by. Free.

### `preview_changes` (~25 tokens)

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

### `quick_check` (~165 tokens)

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.

Input parameters:

- `from` (string, required): Version your code targets, e.g. 14.2.0
- `package` (string, required): Package name or source id, e.g. next, @anthropic-ai/sdk, node. Prefix with npm: or pypi: when a name exists in both registries (pypi:openai vs npm:openai); bare names that match more than one tracked…

### `upgrade_check` (~177 tokens)

What changed in a package since the version your code targets: breaking changes, deprecations, security fixes and major versions crossed (with the official migration guide for each, where one exists), 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).

Input parameters:

- `from` (string, required): Version your code targets, e.g. 14.2.0
- `package` (string, required): Package name or source id, e.g. next, @anthropic-ai/sdk, node. Prefix with npm: or pypi: when a name exists in both registries (pypi:openai vs npm:openai); bare names that match more than one tracked…

### `get_changes` (~138 tokens)

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).

Input parameters:

- `kinds` (string): Comma list of breaking,deprecation,security,release
- `limit` (integer): 1-100, default 20
- `since` (string): ISO date, e.g. 2026-10-01; only changes on or after this
- `source` (string): Source id or package name (npm:/pypi: prefix when ambiguous); omit for all

### `digest` (~70 tokens)

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

Input parameters:

- `kinds` (string): Comma list; default breaking,deprecation,security
- `since` (string): ISO date; default 30 days ago

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-changefeed-api-change-feed/changefeed#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 62
- 2026-11-11: 61
- 2026-11-10: 60
- 2026-11-09: 60
- 2026-11-08: 60
- 2026-11-07: 59
- 2026-11-06: 59

## Common questions

### What is the API Change Feed MCP server?

API Change Feed is an MCP server listed in the public MCP registry as dev.changefeed/api-change-feed. What broke since your version, for 60 popular APIs/SDKs. Free quick check; full reports via x402. This page covers its hosted endpoint (https://changefeed.dev/mcp).

### Is the API Change Feed MCP server safe to use?

API Change Feed scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the API Change Feed MCP server expose?

API Change Feed exposes 6 tools: list_sources, preview_changes, quick_check, upgrade_check, get_changes, digest. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

### Does the API Change Feed MCP server require authentication?

No. We connected to API Change Feed without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the API Change Feed MCP server still maintained?

API Change Feed is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the API Change Feed MCP server?

VerifyMCP ran 11 checks on API Change Feed, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about API Change Feed: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://changefeed.dev/mcp
- Website: https://changefeed.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-changefeed-api-change-feed/changefeed.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-changefeed-api-change-feed/changefeed/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-changefeed-api-change-feed/changefeed.json
- HTML version of this page: https://verifymcp.io/servers/dev-changefeed-api-change-feed/changefeed
