Connect the Uptime Beacon MCP server to the assistant you already use. It reads your monitors and incidents, and creates them once you allow changes. Every failure is still confirmed from a second location first.
Paste this into Claude Code, Codex or Cursor. It reads our llms.txt, connects the server, proposes monitors, heartbeats and watches for what your project runs, and creates them once you approve the list.
Drag the line to compare. Or tap a side to see it whole.
You leave the code, open the dashboard and filter by region, monitor and time until the answer shows up.
Ask where you already are. The assistant reads per-region check history, with DNS, connect, TLS and response timed separately.
MCP is on every plan, Free included. Works with Claude, ChatGPT, Cursor, VS Code, Codex and any MCP client with remote HTTP and OAuth sign-in.
Giving an agent an API key usually means one long-lived secret with every permission, copied into a config file.
You sign in and pick teams. Each one is read-only until you tick Allow changes, with the same roles and plan limits as the dashboard.
No API key to copy for MCP. The JSON API on paid plans uses tokens limited to one team, with separate read and write permissions.
An unsigned webhook is a URL that accepts whatever is posted to it. Your automation cannot tell a real alert from a forged one.
Outgoing webhooks are HMAC-signed. Check the signature with your secret, then open the ticket, alert whoever is on call or run the runbook.
Signed webhooks are on every paid plan. Email and Slack alerts are on every plan, Free included.
Connect your assistant on the Free plan today. Move to Starter when you want the JSON API, signed webhooks, heartbeats for your cron jobs and a second location confirming every failure.
Bigger team? Pro has 1-minute checks, 10 API tokens and unlimited team members.
For a small team running things people pay for.
Billed monthly + VAT
Anything else goes to support@uptimebeacon.eu.
Claude, Claude Code, ChatGPT, Codex, Cursor and VS Code, and any other MCP client that supports remote HTTP servers with OAuth. Give it https://app.uptimebeacon.eu/mcp and sign in.
Not for MCP. Your client registers itself and you approve it in the browser. The JSON API on paid plans uses tokens limited to one team, with separate read and write permissions.
No. With Allow changes it can create, edit, pause and resume monitors, acknowledge or close incidents, start a maintenance window and add heartbeats and watches. Deleting is done in the dashboard.
Not yet. Email, Slack and webhook channels and their routing are set up in the dashboard. New monitors use your team's default alert policy.
No. Our checkers run on the public internet and refuse private and local (localhost) addresses. A job inside your network can report in through a heartbeat with one curl line, on Starter and up.
Create a free account, then add the server to your assistant. Two minutes, no card.