QAmcp
GitHub

How to monitor an MCP server

An uptime check tells you the server answered. Monitoring an MCP server means knowing an AI app can still use it: that it connects, that its tools are still there and still the same, and that nothing unsafe has crept in. This page covers what to watch, how often, and how to set it up.

Last updated: 2 November 2026

Sheet 2 of 4 · What to watch

Seven things that break without an outage

Most MCP breaks don't take the server down. The server keeps answering, and the AI app quietly stops working with it. These are the ones worth an alert.

  1. It stops answering the way an AI app connectsNot just "the link loads", but the MCP handshake: initialize, then tools/list. A server can return a web page or an error on the right link and still fail the handshake.
  2. A tool changedA tool renamed or removed, an input added or made required, a description rewritten. AI apps and saved prompts that relied on the old shape break. Compare each tool list with the last one and alert on the exact lines that changed.
  3. A safety label changedA tool that was marked read-only no longer is, or a delete tool lost its destructiveHint. AI apps use these labels to decide when to ask the user first.
  4. New sentences in a tool descriptionText added to a description is read by the AI. If it tells the AI to do something the user didn't ask for, that is tool poisoning. Every new sentence deserves a look.
  5. A secret shows up in an answer or errorA password, API key or private file path that appears after a deploy, often in an error message.
  6. It gets slow to startMany AI apps give up if connecting and listing tools takes too long. Watch the time to start, not only the time to answer one request.
  7. The login brokeFor servers behind a login: the sign-in setup stops working, or a saved key stops being accepted. Users see "can't connect" while the server itself is fine.
Sheet 3 of 4 · How to set it up

How often to check

Two kinds of check, at two speeds. A quick check (connect and list the tools) every few minutes tells you fast when the server is down. A full test (every safe tool, every label and description) once an hour catches the quieter breaks above. One failed check can be a blip, so check again before you alert, and send one email when a problem starts and one when it's fixed, not one per check.

Do it yourself

The smallest useful check is the first message every MCP app sends. Run it on a schedule (a cron job or any scheduled CI run) and alert when it fails or gets slow:

curl -sS -m 10 -o /dev/null -w "%{http_code} %{time_total}s\n" -X POST https://your-server.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"monitor","version":"1"}}}'

For tool changes, run the free tester on the same schedule against a saved baseline. It shows the exact lines that changed and exits with an error on a change that alters behavior, like a new required input or a changed safety label:

npx qamcp-cli https://your-server.com/mcp --baseline base.json --fail-on-tool-change

Save the baseline once, from a run you're happy with, by adding --save-baseline base.json.

This works, but you build the comparing, the "check again before alerting" and the emails yourself.

With QAmcp Monitor

QAmcp Monitor does all of the above for you, with the same safe-mode test as the free tester. It only runs tools your server labels read-only, and never runs tools that sound like they delete or change something.

Start monitoring freeTest a server first
Sheet 4 of 4 · Questions

Questions

Isn't an uptime check enough for an MCP server?

No. An uptime check tells you the server answered a request. An MCP server can answer and still be unusable for an AI app: a tool renamed, an input removed, a safety label dropped, a login that broke, or answers that suddenly come back empty.

How often should I check my MCP server?

A quick connect-and-list-tools check every few minutes catches outages fast. A full test once an hour catches quieter breaks, like a tool that changed or a score that dropped.

Does monitoring change anything on my server?

Not with QAmcp. Monitor only runs tools your server labels read-only, and only when their name, description and inputs agree. It never runs tools that sound like they delete or change something.

Is there a free way to monitor an MCP server?

Yes. QAmcp Monitor is free for 1 server with email alerts. Once you prove the server is yours, it gets a full test every hour. See pricing.