Skip to content

updown.io MCP by usefulapi

io.usefulapi/updown-iousefulapi.iostreamable-httpv1.40.4Scanned

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

14 tools: 5 can delete or cancel things and 9 only read.

Tools: 5 delete, 0 irreversible, 0 write, 9 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the updown.io MCP by usefulapi can do

The updown.io MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (5 tools: updown_create_check, updown_update_check, updown_add_recipient, updown_create_status_page and 1 more). 9 tools only read.

1 tool reads private data (updown_list_recipients); 3 tools bring in text other people can write (updown_list_downtimes, updown_list_recipients and updown_list_status_pages).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Deletes or cancels 5Claude Code: deny
  • updown_add_recipientAdd an alert recipient: an email address, phone number (sms), webhook URL, Slack-compatible incoming-webhook URL, or Microsoft Teams webhook URL.No findings

    Why it is in this group

    • The name "updown_add_recipient" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Add an alert recipient
    • destructiveHint: true
  • updown_create_checkAdd a new monitoring check.No findings

    Why it is in this group

    • The name "updown_create_check" says "create": a word for a change.
    • The input addresses people (input.recipients): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a check
    • destructiveHint: true
  • updown_create_status_pageCreate a status page showing the given checks, in order.No findings

    Why it is in this group

    • The name "updown_create_status_page" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a status page
    • destructiveHint: true
  • 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).1 finding

    Why it is in this group

    • The name "updown_update_check" says "update": a word for a change.
    • The input addresses people (input.recipients): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...rned by a read-only key hide basic-auth credentials; re-sending such a URL erases them. Req..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update a check
    • destructiveHint: true
  • updown_update_status_pageChange a status page's checks (replaces the list, order respected), name, description, visibility or access key.No findings

    Why it is in this group

    • The name "updown_update_status_page" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update a status page
    • destructiveHint: true
Only reads 9Show 9 read-only tools
  • updown_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 within N days, and whic…No findings

    Why it is in this group

    • The name "updown_find_problems" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find checks with problems
    • readOnlyHint: true
  • updown_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.No findings

    Why it is in this group

    • The name "updown_get_check" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get one check
    • readOnlyHint: true
  • updown_get_check_metricsGet 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.No findings

    Why it is in this group

    • The name "updown_get_check_metrics" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a check's metrics
    • readOnlyHint: true
  • updown_list_checksList all monitoring checks on the account with their status (down, uptime, last_status, error), period, SSL certificate and domain-expiry info.No findings

    Why it is in this group

    • The name "updown_list_checks" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List checks
    • readOnlyHint: true
  • updown_list_downtimesList the downtimes of one check, newest first, 100 per page: error, started_at, ended_at, duration (seconds) and a details URL.Reads text others writeNo findings

    Why it is in this group

    • The name "updown_list_downtimes" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List a check's downtimes
    • readOnlyHint: true
  • updown_list_node_ipsList updown.io's server IP addresses — e.g.No findings

    Why it is in this group

    • The name "updown_list_node_ips" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List monitoring node IPs
    • readOnlyHint: true
  • updown_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 coordinates.No findings

    Why it is in this group

    • The name "updown_list_nodes" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List monitoring nodes
    • readOnlyHint: true
  • updown_list_recipientsList the alert recipients/channels on the account (email, sms, slack, telegram, webhook, zapier, ...).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "updown_list_recipients" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List alert recipients
    • readOnlyHint: true
  • updown_list_status_pagesList the account's status pages: token, public URL, name, description, visibility (public/protected/private) and the ordered check tokens shown.Reads text others writeNo findings

    Why it is in this group

    • The name "updown_list_status_pages" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List status pages
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://updown-io.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://updown-io.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://updown-io.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://updown-io.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http updown-io https://updown-io.usefulapi.io/mcp
claude mcp add --transport http updown-io https://updown-io.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__updown-io__updown_list_checks",
      "mcp__updown-io__updown_get_check",
      "mcp__updown-io__updown_list_downtimes",
      "mcp__updown-io__updown_get_check_metrics",
      "mcp__updown-io__updown_find_problems",
      "mcp__updown-io__updown_list_recipients",
      "mcp__updown-io__updown_list_status_pages",
      "mcp__updown-io__updown_list_nodes",
      "mcp__updown-io__updown_list_node_ips"
    ],
    "ask": [],
    "deny": [
      "mcp__updown-io__updown_create_check",
      "mcp__updown-io__updown_update_check",
      "mcp__updown-io__updown_add_recipient",
      "mcp__updown-io__updown_create_status_page",
      "mcp__updown-io__updown_update_status_page"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as updown-io. Review it before you use it.

Capability tags behind 3 rules
  • mcp__updown-io__updown_list_downtimes untrusted-input
  • mcp__updown-io__updown_list_recipients private-data, untrusted-input
  • mcp__updown-io__updown_list_status_pages untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/updown-io/verify?hash=753e7453666d51ba5ae5d5d43058c506a10a3f34e76e670524f68aa08c4655b6" | jq -e '.changed == false'

Pinned hash 753e7453666d, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/updown-io/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/updown-io
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/updown-io.svg)](https://radar.anlyon.com/servers/io.usefulapi/updown-io)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

updown.io MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the updown.io MCP by usefulapi safe?

No scan can promise that. What its definitions show: 14 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the updown.io MCP by usefulapi delete data?

Yes. 5 tools can delete, cancel or revoke something: updown_create_check, updown_update_check, updown_add_recipient, updown_create_status_page and updown_update_status_page.

Can the updown.io MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the updown.io MCP by usefulapi have?

14 tools: 5 destructive, 9 read. updown_create_check, updown_update_check, updown_add_recipient, updown_create_status_page, updown_update_status_page, updown_list_checks, updown_get_check, updown_list_downtimes and 6 more.

Does the updown.io MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the updown.io MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the updown.io MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.