io.usefulapi/updown-io
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
updown.io MCP by usefulapi
Publisher-provided description
Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.
Summary by lookupd
Lets agents inspect and manage uptime checks, downtimes, metrics, alert recipients and status pages on updown.io.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http updown-io https://updown-io.usefulapi.io/mcp
Codex, remote (streamable-http)
codex mcp add updown-io --url https://updown-io.usefulapi.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"updown-io": {
"url": "https://updown-io.usefulapi.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (14 tools)
Publisher-provided text
updown_list_checksList all monitoring checks on the account with their status (down, uptime, last_status, error), period, SSL certificate and domain-expiry info. Optionally filteupdown_get_checkFetch 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/updown_list_downtimesList 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/dupdown_get_check_metricsGet aggregated metrics for one check over a time range: uptime, apdex, timings (redirect/namelookup/connection/handshake/response/total, ms) and request countsupdown_find_problemsOne-call health overview across every check: which are DOWN (since when, error), which have an invalid SSL certificate, which certificates or domains expire witupdown_list_recipientsList the alert recipients/channels on the account (email, sms, slack, telegram, webhook, zapier, ...). The `id` (e.g. email:3719031852) is what check `recipientupdown_list_status_pagesList the account's status pages: token, public URL, name, description, visibility (public/protected/private) and the ordered check tokens shown. updown: GET /apupdown_list_nodesList 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 coordinupdown_list_node_ipsList 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/nodeupdown_create_checkAdd 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.updown_update_checkChange a check's settings — URL, period, alias, string match, recipients, headers, locations — or pause/resume it (enabled) or mute its alerts (mute_until). Onlupdown_add_recipientAdd an alert recipient: an email address, phone number (sms), webhook URL, Slack-compatible incoming-webhook URL, or Microsoft Teams webhook URL. Returns the neupdown_create_status_pageCreate 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_pageChange a status page's checks (replaces the list, order respected), name, description, visibility or access key. Only the fields you pass are changed. Requires
Details
- Version: 1.37.3
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 472 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/updown-io/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.usefulapi/updown-io)
- 62033 servers
- Last crawl: 2026-11-11T15:38:39.561Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp