mcpbeat Sign in

updown.io MCP by usefulapi MCP Server

answering

updown.io MCP by usefulapi is answering right now. Last checked 1 min ago. It exposes 14 tools. Last commit 10 Oct 2026.

Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
14
Tools
read from the server
113 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day
30 Sep a tool changed version
and 3 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check updown.io MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add updown-io --transport http https://updown-io.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "updown-io": {
      "url": "https://updown-io.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.updown-io]
url = "https://updown-io.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "updown-io": {
      "url": "https://updown-io.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "updown-io": {
      "url": "https://updown-io.usefulapi.io/mcp"
    }
  }
}

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

updown
updown_add_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_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_create_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_find_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_get_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_get_check_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_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_list_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_list_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_list_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_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
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_update_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_update_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.

Endpoints

URLTransportStateLatencyChecked
https://updown-io.usefulapi.io/mcp streamable-http answering 79 ms 1 min ago

Alternatives to updown.io MCP by usefulapi

same job, measured the same way
StatusPal MCP by usefulapi
by usefulapi

Read status-page status, services, incidents and metrics; create, update and publish incidents.

11 tools answering
StatusCake MCP by usefulapi
by usefulapi

Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.

21 tools answering
Instatus MCP by usefulapi
by usefulapi

Manage status pages: components, incidents and maintenances; set live component status.

14 tools answering
Paymo MCP by usefulapi
by usefulapi

Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers.

21 tools answering
Better Stack MCP by usefulapi
by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering
SolidPing
by fclairamb

Self-hostable uptime monitoring: create checks, read incidents, manage status pages.

answering
SutramX
by sutramx

SutramX uptime monitoring: monitors, check results, incidents, status pages and uptime/SLO reports.

361 installs/wk local only
Checkly MCP by usefulapi
by usefulapi

Query Checkly synthetic monitoring — checks, statuses, results, alerts, reporting and dashboards.

22 tools answering

updown.io MCP by usefulapi — questions

Answers built from our own checks of this server.

What can updown.io MCP by usefulapi do?
It exposes 14 tools, read directly from the server on our last check. Among them: updown_add_recipient, updown_create_check, updown_create_status_page, updown_find_problems, updown_get_check, updown_get_check_metrics and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is updown.io MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 113 ms. The bar chart above shows every period we have measured.
How do I connect updown.io MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does updown.io MCP by usefulapi need an API key?
No. updown.io MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is updown.io MCP by usefulapi?
It answers our handshake in 113 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is updown.io MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.