Run on-call from your AI agent.
Connect StatusTick to any agent that speaks MCP with one address. It tells you what is down, checks your code and the vendors you rely on, and updates your status page once you say yes.
Works with
- Claude Code
- Cursor
- VS Code
- Codex CLI
- Windsurf
- Gemini CLI
- Claude Desktop
> Checkout is failing for some users. Is it us or Stripe? Tell customers.
● statustick · list_incidents
Checkout API · open since 14:02 · HTTP 502 · not acknowledged
● statustick · diagnose_dependency stripe
Stripe API is operational. The failure is on your side.
● Search "timeout" in src/payments · Read client.ts
Stripe is fine. Today’s deploy set the payment client timeout to 2 s, and Stripe calls take about 2.4 s. Raise it to 10 s in client.ts:18. I’ll acknowledge the incident and post an update.
● statustick · update_status_update acme.status
Post "Some payments are failing. We found the cause and are fixing it." to your status page?
› 1. Yes
2. Yes, and don’t ask again for this tool
3. No, and tell Claude what to do differently (esc)
Three jobs it takes off your hands.
Set up
Monitoring from your repo
It reads your code and proposes what to watch: your site, a health route, key API routes, scheduled jobs. Nothing is created until you approve the plan.
Read statustick.com/setup.md and follow it.On call
What broke, with your code in view
It reads the incident timeline, who is on call and why an alert was sent, then checks your code and your vendors to find the cause.
Why did checkout alert at 14:02?Tell customers
Status updates, after your yes
It acknowledges and resolves incidents and drafts the status page update. You read it before it goes out.
Post an update and resolve when it’s green.
You decide what it can touch.
When you connect, you sign in and pick read, or read and write. Only owners and admins can give write access. Read and write is needed only to set things up; afterwards you can sign in again with read only.
It can
- Read monitors, uptime, incidents, who is on call and vendor status
- Create monitors: HTTP, TCP, DNS, ping, heartbeats and more
- Pause, mute and plan maintenance on existing monitors
- Acknowledge, resolve and post updates on incidents and status pages
- Change alert policies and public status pages, with write access only
It can’t
- Do more than you allowed. A read-only sign-in only sees read tools.
- Create database or browser checks. Those you set up in the dashboard.
One address to connect.
Add the server to your agent and sign in from the browser. Prefer a key? Create one under Settings, API keys, and keep it in an environment variable, never in a committed file.
$ claude mcp add --transport http statustick \
https://mcp.statustick.comCursor, VS Code, Windsurf and others: add https://mcp.statustick.com as a remote MCP server. Full guide →
Rather click than type? Everything here also works in the dashboard. Join the beta