Skip to content
QuickStatus.dev

Free tools / MCP server checker

MCP server checker

Connect to a remote MCP server the way an agent does: initialize, then tools/list. See the server name, protocol version, transport, every tool, and the step that failed.

MCP server

Streamable HTTP

Sent to that server only, as the Authorization header. Not stored, logged, or put in the share link.

Paste the full endpoint, path included. Tools are listed, never called.

Examples

Example: the handshake works and the server lists 34 tools.

Want an alert when tools/list stops answering? Add an MCP check →

https://api.quickstatus.dev/mcp

Example result
34 tools QuickStatus.dev · protocol 2025-06-18 · JSON replies
StepResultTime
DNS203.0.113.2012 ms
initializeHTTP 200 · protocol 2025-06-18180 ms
initializedHTTP 202 · accepted95 ms
tools/list34 tools110 ms
Server
QuickStatus.dev
Protocol
2025-06-18
Transport
Streamable HTTP · JSON replies · no session id
Capabilities
tools
Total time
420 ms · auth: none sent

Tools

NameDescriptionRequired
usagePlan, caps, and what is in use.—
list_checksList the workspace's checks.—
create_checkCreate an HTTP, heartbeat, MCP, DNS, or TCP check.kind, target
curl: initialize

        

What the MCP checker does

The checker is an MCP client on the Streamable HTTP transport. It sends initialize with protocol 2025-06-18, keeps the Mcp-Session-Id if the server returns one, sends notifications/initialized, then pages through tools/list. Replies can be plain JSON or a text/event-stream; the checker stops reading the stream once the reply arrives. At the end it sends DELETE to close the session.

It never calls a tool. A tool call can change data and needs arguments, so listing is as far as a free, anonymous check should go. Each step opens a fresh connection, so its time includes the TCP and TLS handshake. The whole check has a 12-second limit and runs from Ashburn (us-east-1).

Common failures

What you seeWhat it usually means
401 or 403 on initializeThe server wants a token. If it sends WWW-Authenticate with resource_metadata, it uses MCP OAuth. Paste an access token in Authorization to check what an authenticated client sees.
404 or 405 on initializeWrong path. Streamable HTTP servers take POST on one endpoint, often /mcp. A URL ending in /sse is usually the older HTTP+SSE transport.
406 Not AcceptableThe server wants the client to accept both application/json and text/event-stream. This checker sends both, so a 406 here points at a proxy that rewrites headers.
Reply is not JSON (text/html)A login page, a single-page app's index, or a CDN error page answered instead of the server. Check the route and any auth wall in front of it.
Stream ended without a responseThe server opened an event stream and closed it before sending the reply, often a proxy buffering or timing out SSE.
tools/list returned no toolsThe handshake works but the server exposes nothing. Agents will connect and find nothing to call.

Reproduce it with curl

The snippet under the result sends the same initialize request. Add -i to see the Mcp-Session-Id header you would pass on the next requests.

Frequently asked questions

Is my token stored?
No. It goes in the request to our checker and from there to the server you entered, as the Authorization header. It is not logged, saved, or included in the share link, and the result never repeats it.
Can it check a local stdio server?
No. It reaches servers over the internet. Local, private, and localhost addresses are refused. For a stdio server, run the MCP Inspector on your machine.
It works here. Why won't Claude Desktop or ChatGPT connect?
Chat clients add remote servers as connectors and expect MCP OAuth: a 401 that points at protected-resource metadata, then a sign-in flow. A server that only takes a static bearer key works in Cursor, Claude Code, and Codex, where you put the key in config, but not as a chat connector.
What do the warnings mean?
They point at things agents trip over without the handshake failing: an older protocol version, no tools capability in initialize, duplicate tool names, or tools without a description. Agents choose tools by their description, so an empty one is usually a missed call.
How do I know when the server goes down?
Add an MCP check. It runs this handshake on a schedule from the regions you pick and marks the server down when tools/list fails, returns no tools, or a tool you listed under Expected tools disappears. That can open an incident on your status page.

Know when your MCP server stops answering

A QuickStatus.dev MCP check runs the handshake on a schedule, checks that the tools you expect are still listed, and alerts you by email or Telegram (Slack, Discord, PagerDuty and webhooks on Pro). Free for 10 checks every 5 minutes from 1 region, no card. Agents can set it up through the QuickStatus.dev MCP server.