Remote MCP · Endpoint

API Change Feed MCP server

No. API Change Feed answered an MCP handshake 11 hours ago.

UpLast checked 11 hours ago

Server URL

https://changefeed.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.changefeed/api-change-feed
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
332 ms
Tools exposed
6 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
What broke since your version, for 60 popular APIs/SDKs. Free quick check; full reports via x402.
Listing
From the official MCP registry (active).
Recent checks of API Change Feed
CheckedResultHandshake
11 hours agoHandshake completed332 ms
4 days agoHandshake completed177 ms
14 days agoHandshake completed425 ms

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with API Change Feed and makes no claim about it beyond what these checks measured.