Ask Claude which of your sites are down

Open Claude and type “which of my sites are down?” Claude reads your real monitors and answers. Ask it to show uptime for the API over the last 30 days, or to pause the staging monitor while you deploy, and it does that too.

This works because Uptrack is now listed in Claude’s connector directory. You find it there and connect it in a few clicks. The connector has 16 tools, and every one is limited to your own organization.

One thing first: Uptrack has no free plan. The connector needs an Uptrack account on a paid plan. Pro costs $3/mo and has a 30-day money-back guarantee. Details are at the end.

What you can ask

Claude picks the tool from your question. You do not name tools. These examples show what happens behind a plain sentence.

The check_website tool is the same idea as the public Is website down? tool, and it needs no monitor. Claude asks you to approve each tool call unless you choose “Always allow”.

Connect it

Claude on the web, desktop or mobile

1. Open Customize → Connectors and find Uptrack in the directory.
2. Choose Connect.
3. Sign in to Uptrack. On the consent page, check the scopes and press Allow.

Sign-in uses OAuth 2.0 with PKCE. You paste no API key. The consent page lists the scopes before you approve.

Claude Code

claude mcp add --transport http uptrack https://api.uptrack.app/mcp

Then run /mcp inside Claude Code and follow the steps in your browser to sign in. This is the flow in the Claude Code MCP docs.

Other clients

Any client that supports remote MCP servers and OAuth can use the same URL: https://api.uptrack.app/mcp. The MCP guide has the full tool table and scopes.

The 16 tools

• Read-only (9): list_monitors, get_monitor, get_monitor_analytics, get_monitor_checks, get_dashboard_stats, list_incidents, list_status_pages, list_alert_channels, check_website.
• Write (6): create_monitor, update_monitor, pause_monitor, resume_monitor, acknowledge_incident, create_alert_channel (email, Slack, Discord or Telegram).
• Destructive (1): delete_monitor.

Every tool has a title and read-only, destructive and idempotent hints. Only delete_monitor is marked destructive. The scopes are monitors:read, monitors:write, incidents:read, incidents:write, status_pages:read, alerts:read, alerts:write and analytics:read.

What Claude cannot do yet

The connector does not create status pages, resolve incidents or run browser checks with screenshots. Those stay in the dashboard. Claude can list your status pages and acknowledge an incident, but it cannot do more than that today. The public browser check is a separate page, not a connector tool.

Security and data

• The organization comes from your OAuth token. A tool call cannot read or change another organization.
• A token carries only the scopes you approve. A read-only token cannot call a write tool.
• Uptrack returns only data your account already holds. The server never receives your conversation, only the tool calls Claude makes.
• Email alerts come from Uptrack’s own mail server. No third-party email provider is involved.
• To disconnect, remove the connector in Claude.

Read the privacy policy for the full picture.

About the directory label: Uptrack carries the Community label. Anthropic screens Community connectors automatically, but it has not reviewed them in depth. The listing is not a security audit, and it is not the “Verified” label. Read what each label means and decide for yourself. Check the scopes on the consent page before you press Allow.

Who this is not for

• You do not use Claude or another MCP client. The dashboard and the REST API do the same work.
• You prefer a dashboard-only workflow. A chat adds nothing if you like clicking.
• You want a free plan. The connector needs a paid Uptrack plan.
• You need to create status pages or resolve incidents from chat. Those are not available yet.

More on AI and Uptrack

The AI page explains how Uptrack works with agents. The MCP guide covers setup and the developer endpoints.