About createmcps.com

Why does createmcps.com exist?

MCP shipped its 2026-07-28 specification revision — the largest since the protocol launched. It removes protocol-level sessions, requires new headers on every request, and changes how caching and authorization work. Every MCP server built before it either needs migrating or needs to consciously decide not to, and at the time we started, there wasn't a polished, obvious, free tool that told a developer exactly what was wrong with their server and how to fix it. That gap is what we built.

What should an MCP compliance tool guarantee?

• Every check cites the spec, not a vibe

  75 of the 79 rules link to the exact sentence of the specification they come from. The other 4 are security and registry best practices — labelled as such, not dressed up as spec requirements, because inventing a citation would defeat the point. A wrong “non-compliant” verdict destroys trust instantly, so ambiguous checks are marked warnings, not failures, and every finding carries a dispute link.

• Probing your server should never risk it

  Every probe is read-only — we never call a real tool, read a real resource, or invoke a real prompt — and runs through SSRF-safe admission control before anything is fetched.

• Reports are public, and we'll take yours down on request

  Reports are public by default — that permanence is what makes them citable. Ownership verification isn't built yet, so if a report about your server shouldn't be public, tell us and it goes. See our disclosure policy for how that works.

• The free tier stays free

  Revenue is not the goal that shapes this product. Adoption is. The validator, the full rule catalog, the migration guide, and the CLI are free — always.

What else is createmcps.com building?

The validator is where we start, not where we stop. A formal deprecation policy now exists in the protocol, which means there will be further revisions — so this is built as a permanent MCP compliance tool, not a 2026-07-28 migration tool that dates itself.