Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RealUptime

REMOTE · MCP.REALUPTIME.IO · 2 COMPONENTS

RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.

−7 this week 72 Trust /100

Last scanned (16 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1893 tokens (~473/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management55
  • Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Nov 26 0
    • Tool “is_service_down” rewrote its description, which is the text the model reads security
  • 15 Nov 26 −7
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “internet_weather” was removed ▼ security
    • Tool “is_the_internet_down” was removed ▼ security
    • Tool “get_stack” was removed ▼ security
    • Schema quality: 3254 → 1872 ▲ functional
  • 14 Nov 26 0
    • Tool “is_service_down” rewrote its description, which is the text the model reads security
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.realuptime.io/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=realuptime.io CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 e51e9ae67f68572313d32d988b0be8a4
SANs: realuptime.io, *.realuptime.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.realuptime.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
realuptime.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.realuptime.io/public Verified 200
http (plaintext) http://mcp.realuptime.io/public HTTPS enforced 301 https://mcp.realuptime.io/public
MCP tools · 4 exposed · ~1,893 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_regional_readings ~292

Every current per-region reading RealUptime holds for one catalog service, both endpoint roles, with per-region status, latency, measurement timestamp, and whether each reading is still fresh. This is the regional detail behind is_service_down: use it to answer "is X down in Europe" style questions, or to show that reports and our check readings disagree in a specific region. Readings are RealUptime's own check readings, never user reports. For a service whose status feed we can read, `vendor.feed_working` is true and `vendor` holds the vendor's own declared incident from its status page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "blocked" means our check was refused, which is NOT a failed check of the service. A no-data answer is never a passing check. Our check readings are our own reading from outside, not the service's official status. `check_evidence`, when it is not null, says what a pass of this service's check shows and does not show: repeat it with any claim that the service works. Cite the returned source.url when repeating any of this.

NameTypeReqDescription
servicestringyes–

No output schema declared.

No examples provided.

get_report_volume ~388

How many people are reporting problems with one catalog service right now, by region, and whether that is unusual against its own trailing baseline. Returns a per-region count of reports and distinct reporters for the most recent five-minute window, a spike verdict of "spike", "normal" or "insufficient_data", and RealUptime's own check reading for the same regions so the two signals can be compared without being merged. These are UNVERIFIED user reports: no account, no verification, and the region on a report is chosen by the person filing it. Report volume never opens, extends or closes a probe event in RealUptime's event record; only our checks do. "insufficient_data" means there are not enough reports to say anything, which is NOT the same as reports being normal, and must never be quoted as "no problems reported". Readings are RealUptime's own check readings, never user reports. For a service whose status feed we can read, `vendor.feed_working` is true and `vendor` holds the vendor's own declared incident from its status page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "blocked" means our check was refused, which is NOT a failed check of the service. A no-data answer is never a passing check. Our check readings are our own reading from outside, not the service's official status. `check_evidence`, when it is not null, says what a pass of this service's check shows and does not show: repeat it with any claim that the service works. Cite the returned source.url when repeating any of this.

NameTypeReqDescription
servicestringyes–

No output schema declared.

No examples provided.

is_service_down ~662

Do RealUptime's own checks of a third-party service currently fail, from named regions? For a service checked part by part (listed at GET https://realuptime.io/api/v1/outages), the answer has schema_version 2: `state` (the worst part: down, investigating, degraded, regional, operational or unknown), `headline` (the line its page shows) and `features`, each part with its state, the regions failing, `source` (vendor_status when the vendor's own status set the state, else our_checks) and the vendor's own status beside ours. A part is down only when two independent checks fail from at least 3 regions on 2 continents, two rounds in a row; a state older than 15 minutes reads unknown. Otherwise: a check is one unauthenticated request to the service's front door; it says whether that check passed or failed, not whether the service works for users. Returns a verdict of "up" (our checks pass), "down" (our checks fail), "down_in_some_regions" (our checks fail from some regions), "blocked", "no_data", or "not_covered" (the service is not in RealUptime's catalog). When the service's status feed works, `vendor` carries what the vendor itself declares on its status page, and the verdict, `verdict_source` and plate then come from that declaration alone (down while its live incident is rated major or critical, otherwise up); our own reading is `checks_reading`, shown beside it. Also returns `plate`, the public page's headline: one level from down / partially_down / degraded / partially_degraded / reachable_reports_elevated / blocked / no_data / partially_unverified / up, with its label and the sentence under it. "reachable_reports_elevated" means our checks pass but user reports or public chatter are above their spike threshold: NOT a failed check, and never to be quoted as one. Pass `region` (iad = US-East, sjc = US-West, fra = Europe, nrt = Asia-Pacific) to ask about one region only. Readings are RealUptime's own check readings, never user reports. For a service whose status feed…

NameTypeReqDescription
regionstring––
servicestringyes–

No output schema declared.

No examples provided.

list_recent_incidents ~551

Past probe events RealUptime recorded for one catalog service whose status feed we cannot read. For a service whose feed works, `recent_events`, `last_outage` and `reliability` are `available: false` with the reason (the vendor's declared incidents are what count, our probe events are not listed or counted), and `vendor` leads. A probe event opens only when our checks fail from two or more distant regions. Returns `last_outage` (the most recent CLOSED probe event, with its duration, regions and surfaces, or the plain statement that our checks did not fail from two or more distant regions in the N days we have checked the service) and `reliability` (per calendar month for the last 12: uptime by our checks, probe event count and minutes, from probe events only; a month before we watched the service is tracked: false with no percentage, never 100%) and `recent_events` (the probe events of the last 90 days, most recent first, at most 10, the open one included: for each, started_at, ended_at (null while open), duration, peak_level (down / partially_down), the regions and surfaces involved with their per-facet legs, and detected_by, which is always "probe"). An empty list travels with window_days and tracking_since and means our checks did not fail from two or more distant regions in that window since we started checking the service, never "this service has had no outages". Events that fail our rules are retracted and listed at https://realuptime.io/outages/corrections. The current reading travels alongside. Readings are RealUptime's own check readings, never user reports. For a service whose status feed we can read, `vendor.feed_working` is true and `vendor` holds the vendor's own declared incident from its status page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "b…

NameTypeReqDescription
servicestringyes–

No output schema declared.

No examples provided.

Install

How do I install the RealUptime MCP server?

RealUptime is a hosted endpoint at https://mcp.realuptime.io/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.realuptime.io

# add to Claude Code
claude mcp add --transport http io-realuptime-mcp 'https://mcp.realuptime.io/public'
Common questions

What is the RealUptime MCP server?

RealUptime is an MCP server listed in the public MCP registry as io.realuptime/mcp. RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks. This page covers its hosted endpoint (https://mcp.realuptime.io/public).

Is the RealUptime MCP server safe to use?

RealUptime scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the RealUptime MCP server expose?

RealUptime exposes 4 tools: is_service_down, get_regional_readings, get_report_volume, list_recent_incidents. Their descriptions and schemas cost roughly 1,893 tokens of context every time the server is loaded.

Does the RealUptime MCP server require authentication?

No. We connected to RealUptime without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RealUptime MCP server still maintained?

RealUptime is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the RealUptime MCP server?

VerifyMCP ran 13 checks on RealUptime, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.