MCP standards are arriving fast: server cards (SEP-2127), OAuth metadata (RFC 9728), A2A agent cards, the official registry. But there's no quick way to know whether a server clears the bar. Paste any MCP server URL and get a 0 to 100 readiness score across 5 dimensions, your percentile against every scanned server, and a copy-paste fix for every gap. Useful whether you host an MCP server or build on someone else's. Free, no sign-up.
No reviews yetBe the first to leave a review for Is Your MCP Ready?
Maker
π
Hey Product Hunt π
MCP went from a niche spec to thousands of servers in about a year, and the standards around it are landing fast: an official registry, a Server Card spec for .well-known discovery (SEP-2127), OAuth protected-resource metadata (RFC 9728), an OWASP MCP Top 10. The Linux Foundation's Agentic AI Foundation has been running MCP Dev Summits (NYC, Tokyo, India) all centered on one word: readiness.
The gap I kept hitting: there's no fast way to know whether a given server actually clears that bar. "It works in my client" doesn't tell you if it's discoverable, conformant, or safe to hand an agent.
So I built isyourmcpready.com. Paste any URL, get a 0 to 100 score across 5 dimensions, each mapped to a published spec:
Discoverability: MCP Server Card + registry presence
Protocol Compatibility: lifecycle handshake, version negotiation, transport
Tool Quality: schema + description quality, annotations
Auth & Access: OAuth metadata discoverable, least-privilege
Safety: origin validation, no hard-coded keys, injection-clean descriptions (vs the OWASP MCP Top 10)
Every failing check ships a copy-paste fix prompt, and you get your percentile against every server scanned so far.
It works from both sides: host a server and it's a fix-list; about to wire someone else's into your agent and it's a pre-flight trust check. Read-only, no signup, and every result shows exactly what was and wasn't tested.
Would love to know what your server scores, and whether you'd weight a dimension differently.
Report
This looks super useful. I have been using MCPJam Inspector, but you've addressed some issues that I don't think they cover - like disoverability.
Report
Maker
@tleydenΒ Thank you, that means a lot. Discoverability is a great example. With so much landing around MCP and the adjacent standards, I wanted a single place that surfaces what actually matters when you build and publish a server, instead of everyone having to track every spec themselves.
This looks super useful. I have been using MCPJam Inspector, but you've addressed some issues that I don't think they cover - like disoverability.
@tleydenΒ Thank you, that means a lot. Discoverability is a great example. With so much landing around MCP and the adjacent standards, I wanted a single place that surfaces what actually matters when you build and publish a server, instead of everyone having to track every spec themselves.