Model Context Protocol server for Rollbar
Nothing to run from here
Updown IO is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http updown-io-mcp https://updown-io.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# updown_list_checks, updown_get_check, updown_list_downtimes and 11 more
Updown IO costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http updown-io-mcp https://updown-io.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Only checks in this state (default all). |
| search | string | no | Case-insensitive substring to match against the check URL or alias. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The check's unique token, e.g. ngg8 (from updown_list_checks). |
| metrics | boolean | no | Include performance metrics for the last hour. |
| results | boolean | no | Include detailed results of the last 5 requests (can be large). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The check's unique token, e.g. ngg8 (from updown_list_checks). |
| page | integer | no | Page to fetch (100 per page, default 1). |
| results | boolean | no | Include detailed results (last 5 requests before the downtime and recovery). Can be large. |
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/check
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The check's unique token, e.g. ngg8 (from updown_list_checks). |
| from | string | no | Start time (ISO8601, RFC2822 or YYYY-MM-DD; UTC if no zone). Default: 1 month ago. |
| to | string | no | End time, same formats. Default: now. |
| group | string | no | Group results by 'time' or by 'host' (location). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ssl_days | integer | no | Flag SSL certificates expiring within this many days (default 14). |
| domain_days | integer | no | Flag domains expiring within this many days (default 30). |
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| family | string | no | Address family (default all). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | The URL to monitor, e.g. https://example.com, tcp://host:port, icmp://host. Omit for pulse checks. |
| type | string | no | Check type; inferred from the URL by default — mainly useful for 'pulse'. |
| period | integer | no | Interval in seconds. Regular checks: 15, 30, 60, 120, 300, 600, 1800 or 3600 (default 60). Pulse checks: anywhere from 15 s to 1 month. |
| apdex_t | number | no | APDEX threshold in seconds: 0.125, 0.25, 0.5, 1.0, 2.0, 4.0 or 8.0 (default 0.5). |
| enabled | boolean | no | Whether the check runs. false pauses it (reversible). |
| published | boolean | no | Whether the check's public status page is visible (default false). |
| alias | string | no | Human-readable name for the check. |
| string_match | string | no | Text that must appear in the response. For TCP/TCPS checks, '<closed>' inverts the check (alert if the port is open). |
| mute_until | string | no | Mute notifications until a time (ISO8601, e.g. 2026-10-01T08:00:00Z), or 'recovery', or 'forever'. |
| http_verb | string | no | HTTP verb for the request (default GET/HEAD). |
| http_body | string | no | HTTP body sent with the request. |
| disabled_locations | array | no | Monitoring locations to disable: lan, mia, tor, rbx, fra, cap, hel, sin, tok, syd. |
| recipients | array | no | Alert recipient ids to select, e.g. ['email:12345', 'sms:67890'] (from updown_list_recipients). |
| custom_headers | object | no | HTTP headers updown sends with each request, e.g. { "X-Api-Key": "..." }. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The check's unique token, e.g. ngg8 (from updown_list_checks). |
| url | string | no | New URL to monitor (not for pulse checks). |
| period | integer | no | Interval in seconds. Regular checks: 15, 30, 60, 120, 300, 600, 1800 or 3600 (default 60). Pulse checks: anywhere from 15 s to 1 month. |
| apdex_t | number | no | APDEX threshold in seconds: 0.125, 0.25, 0.5, 1.0, 2.0, 4.0 or 8.0 (default 0.5). |
| enabled | boolean | no | Whether the check runs. false pauses it (reversible). |
| published | boolean | no | Whether the check's public status page is visible (default false). |
| alias | string | no | Human-readable name for the check. |
| string_match | string | no | Text that must appear in the response. For TCP/TCPS checks, '<closed>' inverts the check (alert if the port is open). |
| mute_until | string | no | Mute notifications until a time (ISO8601, e.g. 2026-10-01T08:00:00Z), or 'recovery', or 'forever'. |
| http_verb | string | no | HTTP verb for the request (default GET/HEAD). |
| http_body | string | no | HTTP body sent with the request. |
| disabled_locations | array | no | Monitoring locations to disable: lan, mia, tor, rbx, fra, cap, hel, sin, tok, syd. |
| recipients | array | no | Alert recipient ids to select, e.g. ['email:12345', 'sms:67890'] (from updown_list_recipients). |
| custom_headers | object | no | HTTP headers updown sends with each request, e.g. { "X-Api-Key": "..." }. |
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 A
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Recipient type. |
| value | string | yes | The email address, phone number or URL. |
| name | string | no | Optional friendly label (webhooks only at the moment). |
| selected | boolean | no | true (default) = selected on all existing checks; false = not selected on any check. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| checks | array | yes | Check tokens to show, in display order, e.g. ['dmbe', 'ngg8']. |
| name | string | no | Name of the status page. |
| description | string | no | Text displayed below the name (supports newlines and links). |
| visibility | string | no | Page visibility (default public). |
| access_key | string | no | Access key for protected pages (defaults to a random 30-byte string). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The status page's unique token, e.g. 3ji4k (from updown_list_status_pages). |
| checks | array | no | New ordered list of check tokens to show (replaces the current list). |
| name | string | no | Name of the status page. |
| description | string | no | Text displayed below the name (supports newlines and links). |
| visibility | string | no | Page visibility (default public). |
| access_key | string | no | Access key for protected pages (defaults to a random 30-byte string). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Updown IO or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Updown IO can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.