App Finishers

Free tool · no sign-up · a few seconds

Test your MCP server online

Paste your server's URL. We connect the way Claude, Cursor and the directories do: initialize, then list the tools. You see whether a client gets in and, if not, why and what to change.

Remote servers over https only. We never call your tools and never send a key.

What it checks

A server that asks for a key, limits the rate or speaks only the newest protocol version has answered, so we say so instead of calling it down. A sign-in that clients can't complete is different: we name the step where it stops.

Why servers fail

This month, 1 in 20 company MCP servers in the official registry failed this check twice. The causes, and a fix for each, are in the state of MCP servers.

Questions

Is it free?

Yes, with no sign-up and no email, up to 10 tests an hour.

Do you call my tools?

No. We send initialize, the initialized notification and tools/list, as directories do. When a server asks for sign-in, we also read its public sign-in metadata. Nothing else.

It works in my client but fails here. Why?

We test from Cloudflare's network, not your machine. A server that only listens on localhost or a private network, allows only some IP ranges, or needs a key in the URL works for you and fails for everyone else, including directories.

What do you keep?

The address you tested and its result, for up to 30 days, to spot common problems. Nothing about you. See Privacy.