MCP server for uptime monitoring
Let any AI agent create, check, and manage your monitors itself.
Your monitors, in your agent's hands
UpCheck ships a remote MCP server, so any Model Context Protocol client, Claude or your own agent, can manage monitors on your behalf. Say "monitor my site" and the agent drives the rest.
The server exposes five tools: list_monitors for current status and 24h stats, create_monitor (only a URL required), update_monitor (including enabled: false to pause), delete_monitor, and test_monitor to run one check against a draft config without saving. It speaks stateless streamable HTTP, which every current MCP client supports; there is nothing to install or host.
claude mcp add --transport http upcheck \
https://upcheck-api-a.rekwiem.com/mcp \
--header "Authorization: Bearer upk_your_key"Agents that set up their own monitoring
The interesting flow isn't you asking an agent to make a monitor. It's the agent doing it unprompted: it deploys a service, calls test_monitor to confirm the endpoint answers, then create_monitor to register it, and the thing it just shipped is being watched before the deploy log scrolls away.
Because create returns the first check's result, the agent knows immediately whether it pointed the monitor at the right URL, and can correct itself without a human in the loop.
Scoped to one project, by construction
Authentication is a Bearer project API key, created in your project's Settings under Access tokens. A key binds to one project, so the agent can only touch that project's monitors; it can never create more keys or reach account settings.
Give the key an expiry for throwaway experiments, and revoke it any time from the same list. In clients with a connector UI, paste the endpoint and set the Authorization header; for clients configured by file, the JSON above is the whole setup.