Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks. For developers and site owners who monitor uptime with updown.io. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"updown-io": {
"url": "https://updown-io.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"updown-io": {
"type": "http",
"url": "https://updown-io.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The AI gives an overview of all checks: which are down and since when, which have an invalid SSL certificate, and which certificates or domains expire soon.
updown_find_problems updown_list_checks
The AI reads a check's uptime, apdex and timings over a time range. Timings can also be grouped by time or by monitoring location, without uptime.
updown_get_check_metrics updown_get_check
The AI lists a check's downtimes with error, start, end and duration. You see which checks had problems and for how long.
updown_list_downtimes updown_list_checks
The AI creates a new check for a URL or heartbeat, or changes the URL, period, alias or alert recipients of a check, pauses it or mutes its alerts.
Changes data · updown_create_check updown_update_check updown_list_recipients
The AI adds an alert recipient such as an email or Slack webhook, and creates or updates a status page that shows chosen checks.
Changes data · updown_add_recipient updown_create_status_page updown_update_status_page
The login page asks for your Updown.io API key.
Find it at updown.io → **Settings → API keys**. The read-only key is enough for every read tool (checks, downtimes, metrics, problems, recipients, status pages); to create/update checks, add recipients or edit status pages, paste the read/write key instead. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Updown.io API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the updown.io connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
updown_list_checks | read | List checks List all monitoring checks on the account with their status (down, uptime, last_status, error), period, SSL certificate and domain-expiry info. Optionally filter client-side by status or a text match on URL/alias. updown: GET /api/checks. |
updown_get_check | read | Get one check Fetch a single check by token, optionally with the last hour of performance metrics and/or the detailed results of the last 5 requests. updown: GET /api/checks/:token. |
updown_list_downtimes | read | List a check's downtimes List the downtimes of one check, newest first, 100 per page: error, started_at, ended_at, duration (seconds) and a details URL. updown: GET /api/checks/:token/downtimes. |
updown_get_check_metrics | read | Get a check's metrics Get aggregated metrics for one check over a time range: uptime, apdex, timings (redirect/namelookup/connection/handshake/response/total, ms) and request counts by response time. Optionally group by 'time' or by 'host' (monitoring location). Data is hourly (daily after 2 days, monthly after 40 days); the range must span at least one hour. Uptime is not returned when grouping. updown: GET /api/checks/:token/metrics. |
updown_find_problems | read | Find checks with problems One-call health overview across every check: which are DOWN (since when, error), which have an invalid SSL certificate, which certificates or domains expire within N days, and which checks are paused or muted. Built from GET /api/checks. |
updown_list_recipients | read | List alert recipients List the alert recipients/channels on the account (email, sms, slack, telegram, webhook, zapier, ...). The `id` (e.g. email:3719031852) is what check `recipients` take. updown: GET /api/recipients. |
updown_list_status_pages | read | List status pages List the account's status pages: token, public URL, name, description, visibility (public/protected/private) and the ordered check tokens shown. updown: GET /api/status_pages. |
updown_list_nodes | read | List monitoring nodes List updown.io's monitoring/webhook servers keyed by location code (lan, mia, tor, rbx, fra, cap, hel, sin, tok, syd) with IPv4, IPv6, city, country and coordinates. Public — no API key needed. updown: GET /api/nodes. |
updown_list_node_ips | read | List monitoring node IPs List updown.io's server IP addresses — e.g. to allowlist the monitors in a firewall. Choose all, ipv4 or ipv6. Public — no API key needed. updown: GET /api/nodes/ips, /api/nodes/ipv4, /api/nodes/ipv6. |
updown_create_check | write | Create a check Add a new monitoring check. The type (http, https, tcp, tcps, icmp) is inferred from the URL scheme; pass type 'pulse' (and no URL) for a cron/heartbeat check. Each check consumes updown credits while enabled. Requires the read/write API key. updown: POST /api/checks. |
updown_update_check | write | Update a check Change a check's settings — URL, period, alias, string match, recipients, headers, locations — or pause/resume it (enabled) or mute its alerts (mute_until). Only the fields you pass are changed. Caution: URLs returned by a read-only key hide basic-auth credentials; re-sending such a URL erases them. Requires the read/write API key. updown: PUT /api/checks/:token. |
updown_add_recipient | write | Add an alert recipient Add an alert recipient: an email address, phone number (sms), webhook URL, Slack-compatible incoming-webhook URL, or Microsoft Teams webhook URL. Returns the new (or already-existing) recipient with its id. By default it is selected on ALL existing checks; pass selected=false to add it unattached. Slack/Telegram/Zapier/Statuspage integrations must be set up in the web UI. Requires the read/write API key. updown: POST /api/recipients. |
updown_create_status_page | write | Create a status page Create a status page showing the given checks, in order. Returns its token and URL. Requires the read/write API key. updown: POST /api/status_pages. |
updown_update_status_page | write | Update a status page Change a status page's checks (replaces the list, order respected), name, description, visibility or access key. Only the fields you pass are changed. Requires the read/write API key. updown: PUT /api/status_pages/:token. |
updown_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
updown_request_feature | Request a missing feature Tell usefulapi that the user needs something the updown.io tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
updown_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on updown.io (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
updown_cancel_subscription | Cancel the Pro subscription Cancel the caller's updown.io Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run updown_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this updown.io server only. Subscribe with updown_upgrade (it returns a Stripe Checkout link). Cancel any time with updown_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running updown_upgrade before then undoes the cancel. Or write to [email protected].
Check downtime, SSL certificates and domain expiry. Report uptime and response times of a site. List the downtimes of a check. Add a check or change an existing one. Set up alert recipients and a status page. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by updown.io. The server calls the updown.io API with your own updown.io access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Updown.io API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Updown.io API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the updown.io API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in updown.io.
Yes, if you approve it. 5 of the 14 updown.io tools can create or change data. The other 9 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this updown.io server only. Cancel any time: Pro then runs to the end of the paid period. Run updown_usage_status to see how many calls you used.
Ask the AI to run updown_upgrade: it returns a Stripe Checkout link. To cancel, run updown_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with updown_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.