Fix guides · check protocol.version

Upgrade your MCP SDK to a current protocol revision

Servers that only speak 2024-11-05 miss structured output, annotations, elicitation and the current auth model.

3,251 of 15,360 reachable MCP servers (21.2%) have this issue today.

Why it matters

Clients negotiate the newest revision both sides support. A server stuck on the first revision forces every client back to it. Upgrading the official SDK is usually enough.

What to do

TypeScript: npm i @modelcontextprotocol/sdk@latest · Python: pip install -U mcp

Check your server

Paste your endpoint at /check, or run it in CI:

pipx run glimind check https://your-server.example.com/mcp --min-grade B