Your MCP servers, on patrol around the clock.
MCPatrol probes every MCP server you register, day and night, and puts the incident on your phone before your users hit it — health, latency history, and alerts when a server's tools change, not just when it goes down.
Android · coming soon to Google Play.
The incident finds you.
A cloud prober checks every server you register, every few minutes, from outside your network. When one stops answering — or starts failing its MCP handshake — an incident opens and lands on your phone as a push notification, with recovery notice when it comes back.
Open incidents sit on the front page until they're resolved. Resolved ones get out of the way.
History, not vibes.
Every probe outcome is recorded: state, latency, timestamp. Server pages show the check history, latency percentiles, uptime over 7/30/90 days, and mean time to recovery — real recorded numbers, never estimates.
When a value isn't known, MCPatrol shows a dash. It never invents data.
Most monitors tell you when a server dies.
MCPatrol tells you when it changes.
MCP servers expose tools, resources, and prompts — and those inventories change under you. MCPatrol snapshots the full inventory on every examine and diffs it: a new tool appearing, a schema quietly dropping, a prompt renamed. You get the change feed and a push, the moment it happens.
If an upstream update adds a tool you didn't expect, you'll know before your agents do.
stdio servers on your PC, visible on your phone.
Plenty of MCP servers never touch the network — they run over stdio on your workstation. The MCPatrol bridge is a small agent that relays them to your estate, so the servers on your desk get the same monitoring, inventory tracking, and per-request traffic metadata as your hosted ones.
Track your listings, not just your uptime.
Shipping an MCP server means getting listed — the official MCP registry, mcp.so, Glama. MCPatrol checks whether each of your servers is actually listed, builds the server.json manifest for you, and walks you through each registry's submission with copy-ready fields.
Your data, plainly
Local mode
No account, no cloud: servers and probe history stay in the app's database on your device. Nothing is sent anywhere.
Delete in-app
One button removes your account and every row it owns — servers, history, incidents, tokens. Immediate, complete, verified.
No trackers
No advertising SDKs, no analytics SDKs, no location, no contacts. Push notifications are the only third-party service involved.
Locked down
TLS everywhere, per-account API keys, passwords stored only as salted PBKDF2 hashes. Details in the privacy policy.
Each of these is a mechanism in the shipped code, not a certification mark — the security page says how to verify them and how to report what we missed.
Put your estate on patrol.
MCPatrol is coming to Google Play. Watch your MCP estate from your phone.
Get launch updates