MyMCPTools
Live MCP handshake verification

MCP server status

Is that MCP server actually up? We verify Model Context Protocol servers with a real handshake — not a status-code ping — so you can see which are live, which need auth, which are down, and which just changed their tools. Last refreshed 1m ago.

5
Verified live
38
Auth required
0
Limited
1
Down

44 remotely-verifiable servers probed · 2,396 local/stdio installs (no remote endpoint to verify).

Down or degraded

Servers that failed the MCP handshake on recent checks, or that speak MCP but returned no tools.

  • Needle

    · 711 ms · Needle AI

    Down· 1m ago

Verified live servers

Completed a full MCP handshake and exposed tools on the last check, fastest handshake first.

Recently changed tools

Servers whose tool schema changed since the previous probe — added, removed or renamed tools. Worth re-checking before you rely on them.

Auth required

Alive and speaking MCP, but gated behind OAuth/Bearer auth — you will need credentials to connect.

Need this data in your app?

The Trust Data API serves live verdict, latency, uptime and tool-schema drift for every server on this page as JSON and CSV — so your agent or gateway can route only to healthy MCP servers.

Explore the status APIBrowse all MCP servers

MCP server status FAQ

How do you check whether an MCP server is down?

We run a real Model Context Protocol handshake against each remote server — initialize, notifications/initialized, ping and tools/list over Streamable HTTP — not a plain HTTP status ping. A server that returns 200 from a misconfigured proxy but never completes the MCP handshake is reported as Down, not healthy. Probes are strictly read-only and never call a server's tools.

What do the status labels mean?

Live means the server completed a full MCP handshake and exposed tools. Limited means it speaks MCP but returned no or partial tools. Auth required means it responded with a 401 and an OAuth/Bearer challenge, so it is alive but gated. Down means it failed the handshake on several consecutive checks. Local install means it is a stdio/local server with no remote endpoint to verify.

Why are so many servers marked "Local install"?

Many MCP servers ship as npm or pip packages that run on your own machine over stdio. There is no remote endpoint to handshake, so they cannot be verified live — we surface source-repo recency instead on each server's page.

How fresh is this data?

The full population is re-probed on a nightly cadence, with a hot set of popular and recently-failing servers checked more often. Each server shows its own last-checked time.

Can I get this data programmatically?

Yes. The Trust Data API exposes live verdict, latency, uptime and tool-schema drift as JSON and CSV endpoints. See the developers page for endpoints and API keys.