Paste a server URL. McpFit runs the real handshake, checks it against the current spec and the incoming breaking changes, and tells you exactly what to fix — not just that something's wrong.
No install, no signup for a single check. McpFit is a stateless prober — it doesn't store your server, doesn't hold a session, just runs the handshake live and tells you what it saw.
Paste your MCP server's endpoint. Streamable HTTP, JSON or SSE responses — both are handled.
initialize → notifications/initialized → tools/list, timed and inspected against every rule.
Every failing rule ships with a specific fix_suggestion — what to change and why, in plain language.
The MCP spec is a release candidate. If it changes at the last minute, we don't want to be shipping a code deploy under deadline pressure — we flip a status field.
Every rule is either stable (blocks your badge if you fail it) or upcoming (informational, shown with a fix ahead of time). When 2026-07-28 locks, upcoming rules just flip to stable — no engine changes.
Free, no account. Results are never stored — every check is a fresh probe.
The badge is live, not cached — it re-runs the check on every render, so it's never stale.
The GitHub Action calls the same live endpoint — one source of truth between your terminal, your README badge, and your pipeline.