Free MCP server test
Test your MCP server online: can people find it?
Paste your endpoint. In about ten seconds you'll see whether it answers like an MCP server, whether it's in the official registry, and whether its landing page can rank on Google and in AI search.
Free, no sign-up. We send one MCP initialize request and never call your tools.
Three checks that decide whether you get installs
It works
Directories health-check your endpoint. A failed handshake or an undiscoverable sign-in gets you marked as down.
It's listed
The Official MCP Registry feeds GitHub's MCP Registry, PulseMCP and several clients. Missing there means missing in many places.
It can be found
Your landing page needs to be indexable, say MCP and show setup steps, so it ranks when people search for a server like yours.
How is this different from MCP Inspector?
MCP Inspector is the official developer tool you run locally to connect to a server and call its tools by hand. This test runs from the public internet, so it shows what directories and clients see: whether the handshake and OAuth sign-in work, whether you are in the official MCP registry, and whether your landing page can rank. Use both.
What does the MCP server checker test?
It sends one MCP initialize request to your endpoint, checks whether sign-in uses discoverable OAuth, searches the Official MCP Registry for your namespace or endpoint, and reads your landing page for the signals that decide whether people find it: indexable, says MCP, has a title, description and setup snippet.
Does it call my tools or need my API key?
No. It only sends the initialize handshake, the same first message every client sends, and reads public pages. It never lists or calls tools and never asks for credentials.
My server requires sign-in. Will it fail?
No. A 401 that points clients to OAuth discovery is how private remote servers should behave, and the check treats it as healthy. Without OAuth discovery, clients need an API key header and some directories cannot health-check you.
Why does the landing page matter for an MCP server?
Directories link to it, and people search Google and AI assistants for "<tool> mcp". If that page is not indexable, never says MCP or has no setup steps, the listing traffic leaks away and you miss the search traffic.