Will Claude, Cursor and ChatGPT connect to your MCP server?
A free, open-source check of your own MCP server, done the way these clients connect: protocol version, OAuth sign-in and tool definitions. Results in plain language, in a few seconds.
npx mcp-compat-check https://mcp.yourcompany.com/mcpNeeds Node.js 20 or newer. Add --json for machine-readable output (handy in CI). Source: github.com/franckyo/mcp-compat-check (MIT).
Example output
https://mcp.example.com/mcp Problems found that stop clients from working (1 problems, 1 risks, 2 passed) i The server requires sign-in ✓ 401 includes a WWW-Authenticate challenge Clients know how to start signing in. ✖ OAuth metadata names a different server Clients such as Cursor reject the sign-in because the metadata says the server is "http://internal-host:8080/mcp", not https://mcp.example.com/mcp. Often a wrong public-URL setting behind a proxy or custom domain. ✓ PKCE (S256) supported Clients can complete the secure sign-in flow. ! Only Dynamic Client Registration supported Works today. The 2026-07-28 spec prefers Client ID Metadata Documents and deprecates DCR, and fixed redirect-URI allowlists on DCR are a common reason new clients get blocked.
Real output for an example server with a common proxy misconfiguration (evidence lines trimmed).
What gets checked
- Current spec (2026-07-28): whether clients that open with the new handshake can connect directly.
- Protocol negotiation: the version your server agrees on and whether it handles newer clients.
- OAuth sign-in: the discovery documents Claude.ai, ChatGPT and Cursor read, including the server-URL mismatch that makes Cursor refuse to log in, PKCE, and self-registration.
- Tools: valid JSON Schemas, names and duplicates, the things that make clients drop tools or the whole server.
- Sessions: servers that reject their own session (common behind load balancers).
What it never does
It never calls tools, sends credentials, changes data or follows redirects, and it never connects to private or internal addresses (every DNS answer is checked at connect time). Only the standard client handshake is used. Run it on servers you own or operate.
Want these fixed?
I fix MCP servers for a fixed price, agreed before any work starts: spec upgrades, OAuth sign-in for Claude and ChatGPT connectors, broken tools, SDK migrations. Payment is 50% to start and 50% on delivery.
Email me your server URL and the check's output, and I'll reply within one business day with a quote.
Email me for a quote