MCP changelog and versions
Server versions and the protocol versions it speaks.
Protocol versions
One endpoint answers every version below. The server keeps no session and no stream: replies are plain JSON on a POST, and notifications get 202. It does not batch.
| Version | What it means here |
|---|---|
2026-07-28 | the current protocol: stateless; every request carries _meta with the protocol version and client capabilities; results carry resultType, ttlMs and cacheScope |
2025-11-25 | the earlier protocol: the client sends initialize first, results are plain |
2025-06-18 | the earlier protocol: the client sends initialize first, results are plain |
2025-03-26 | the earlier protocol: the client sends initialize first, results are plain |
Ask the server itself with server/discover: it lists the supported versions and its own version.
Server versions
- 1.1.0
- 2026-10-29. Prompts (
build_plan,compare_on_topic,review_design). Keys can expire (30, 90 or 365 days) and can be rotated. Test my key in the app. Rate-limit headers on every reply and Retry-After on every 429. This documentation, client setups and llms.txt. - 1.0.0
- 2026-10-27. The first release: 8 tools, API keys with scopes free and free+ask, per-key limits, both protocol eras.
What is not built yet
- OAuth sign-in for MCP, which one-click connectors in claude.ai and ChatGPT need. Keys work in every client on the clients page; OAuth is next if the demand is there.
- A REST mirror of the tools, with an OpenAPI file. MCP over HTTP and curl cover the use today.
- Resources and argument completion for prompts.
Tell the owner of the service which one you need.