MCP server monitoring
An MCP server can return 200 and still be broken for agents. The handshake times out, tools/list fails, or a deploy drops a tool. A plain HTTP check misses all three.
A QuickStatus.dev MCP check speaks the protocol. It runs initialize and tools/list on a schedule, and alerts you when either one fails.
What an MCP check verifies
- The server answers the MCP
initializehandshake. tools/listreturns at least one tool.- Every tool you list under Expected tools is still there.
- Optional: the response comes back under your Slow above (ms) limit.
- On https URLs: the certificate is valid, with a warning 7, 14 or 30 days before it expires.
Tools are listed, never called. The check does not run your tools.
Behind auth? Add a header
Under Authorization, add request headers such as Authorization: Bearer <token>. The check then sees what an authenticated client sees.
Alerts without the noise
One failed run is recorded, not sent. The check goes down after 1, 2, 3 or 5 failed runs in a row (default 3). Then one alert goes out.
Alerts go to email and Telegram on Free. Pro adds Slack, Discord, PagerDuty, Pushover and webhooks. Link the check to a status-page component, and a confirmed failure can open an incident for your users.
Set it up in a minute
- Open Checks and click Add check.
- Pick MCP server and paste the URL (for example
https://example.com/mcp). - Optional: add an Authorization header and your Expected tools.
- Click Add check. The first run starts right away.
Prefer the API? Create it with "type": "mcp", the server URL as target, and mcp_expected_tools. Or ask Claude Code, Cursor or Codex to do it through the QuickStatus.dev MCP server.
Pricing
- Free: 10 checks (HTTP, MCP, DNS, TCP, heartbeat or server), every 5 minutes from 1 region, 14 days of results. No card.
- Pro, $15/month: 25 checks, every 60 seconds from 5 regions, 90 days of results.
MCP server monitoring FAQ
What is the difference from an HTTP check?
An HTTP check only proves the URL answers. An MCP check runs the real handshake and lists the tools, so it catches a server that answers but no longer works for agents.
Does the check call my tools?
No. It runs initialize and tools/list only. Tools are listed, never called.
Can I monitor a server that needs a token?
Yes. Add the header under Authorization, for example Authorization: Bearer <token>.
Is MCP server monitoring free?
Yes. Free includes 10 checks, and MCP checks count like any other. They run every 5 minutes from 1 region, with email and Telegram alerts.