Only 7 of 72 MCP endpoints answered on the newest revision. The other 65 used older ones.

By Lior AharonovFounder, 7IT Solutions · 2 October 2026

What happened

An independent count published on 2 October 2026 sent an initialize request to 186 remote MCP endpoints from the official registry on 1 and 2 October. Of the 72 that returned a protocol version, 7 (9.7%) negotiated the newest revision, 2026-07-28, and the rest answered with one of four older ones; 86 sat behind a sign-in.

Why it matters

Clients and servers will be on different revisions for a while, so a server that still negotiates the older ones cleanly gets reached by more agents. The author is upfront that the 186 are a slice of the registry by hostname, not a random sample.

What to do

Send your own server an initialize request right now and see which revision it answers with. Keep the older revisions working until your clients have actually moved.

The newest spec gets the blog posts. The older ones still do most of the talking.

Lior Aharonov · my take

Sources

The MCP Ecosystem Is Speaking Five Revisions at Once. Here Is the Dated Count. (Pennyforge, DEV Community) dev.to

protocolresearch

Researched with AI tools; every fact is checked against the linked sources.