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.

io.github.cyanheads/ioda-outages-mcp-server

REMOTE · IODA-OUTAGES.CASEYJHAND.COM · 2 COMPONENTS

Investigate Internet outages with IODA events, alerts, and connectivity signals via MCP.

+6 this week 79 Trust /100

Last scanned (21 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 4 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 Security83
Transport & Reachability100
Schema Quality & AI Usability71
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3843 tokens (~549/item across 7 items; 6 tools + 1 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “ioda_get_signals” rewrote its description, which is the text the model reads security
    • Tool “ioda_get_alerts” rewrote its description, which is the text the model reads security
    • Tool “ioda_summarize_outages” rewrote its description, which is the text the model reads security
    • Tool “ioda_search_entities” rewrote its description, which is the text the model reads security
    • Schema quality: good → excellent functional
    • Server version: 0.3.0 → 0.3.1 functional
    • “ioda_get_alerts” reworded the description of “from” cosmetic
    • “ioda_find_outages” reworded the description of “limit” cosmetic
    • “ioda_find_outages” reworded the description of “from” cosmetic
    • “ioda_get_alerts” reworded the description of “limit” cosmetic
    • “ioda_summarize_outages” reworded the description of “limit” cosmetic
    • “ioda_summarize_outages” reworded the description of “from” cosmetic
    • “ioda_search_entities” reworded the description of “query” cosmetic
    • “ioda_search_entities” reworded the description of “limit” cosmetic
    • “ioda_get_signals” reworded the description of “source” cosmetic
    • “ioda_get_signals” reworded the description of “maxPoints” cosmetic
    • “ioda_get_signals” reworded the description of “from” cosmetic
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +3
    • Schema quality: 571 → 504 ▲ functional
    • First check of Schema quality: 100 functional
    • Schema quality: excellent → good functional
    • New resource “ioda-outages-guide” functional
    • Server version: 0.2.1 → 0.3.0 functional
  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 24 Oct 26 71

    First indexed and scored.

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 4 Nov 2026 · Probed https://ioda-outages.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 995a30681ab772540e934241ca1d576c
SANs: caseyjhand.com, *.caseyjhand.com
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 secure

Validation of ioda-outages.caseyjhand.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
ioda-outages.caseyjhand.com. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ioda-outages.caseyjhand.com/mcp Verified 200
http (plaintext) http://ioda-outages.caseyjhand.com/mcp HTTPS enforced 301 https://ioda-outages.caseyjhand.com/mcp
MCP tools · 6 exposed · ~3,382 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
ioda_find_outages ~718

Find IODA outage events overlapping an explicit Unix-second window of at most 31 days. Omit entity filters for global scope, which searches one day outside the window by default instead of 14; global searches over multi-day windows can time out, so narrow the window or add entityType. A code requires its entityType. relatedToType and relatedToCode limit results to entityType entities within one country, region, ASN, or geoasn. Source scores are not an absolute severity scale. Starts at until are included; adjacent windows can duplicate boundary detections. Starts may precede from; ends can be clipped at until and do not establish recovery. ignoreMethods excludes source.method, source.*, or *.method upstream before scoring. includeAlerts adds nested transitions and can increase size. Pages are zero-based; keep filters and limit fixed.

NameTypeReqDescription
entityCodestring–Two-letter country code, IODA numeric region code, decimal ASN (AS prefix accepted), or geoasn code joining an ASN and a region or country code (40934-576, 59962-IR); resolve names with ioda_search_e…
entityTypestring–country, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
extendWindowSecondsinteger–Seconds before from to search for the start of an event overlapping the window, and after until for its recovery; only overlapping events are returned. Defaults to 1209600 (14 days) with entityType a…
fromintegeryesInclusive Unix seconds UTC; no milliseconds; window at most 31 days. IODA's API holds no outage detections before 2022-01-26 UTC.
ignoreMethodsarray–Detection methods to exclude upstream before event construction and scoring; duplicates are removed, and an empty array excludes nothing. Keep fixed across ranking and drill-down calls.
includeAlertsboolean–Include original nested alert transitions and baselines; may substantially increase response size.
limitinteger–Default 20; a larger value returns at most 1000 and says so. Keep fixed when continuing.
pageinteger–Zero-based upstream page; restart at 0 when changing limit.
relatedToCodestring–Scope entity code, normalized like entityCode for relatedToType (IR, 1829, AS42337, 60627-IR); resolve names with ioda_search_entities. Provide with relatedToType.
relatedToTypestring–Scope type: country, region, asn, or geoasn. With relatedToCode, returns entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and excludes e…
sourcestring–bgp, ping-slash24, merit-nt, or gtr; blank means all sources. Case and whitespace are normalized.
untilintegeryesInclusive Unix seconds UTC for transition/event-start selection, after from and no later than now; adjacent windows can duplicate boundary detections.
NameTypeReqDescription
appliedobject–Every normalized input, effective window, filter and pagination value.
errorobject–Present when the call failed. Absent on success.
eventsarray–Original outage events and source scores without merging or ranking.
noticestring–Result interpretation and concrete next call.
paginationobject–Upstream page and possible continuation.
provenanceobject–Endpoint and original source attribution.
truncatedobject–A full page may have further records; not an exact total.

No examples provided.

ioda_get_alerts ~680

Retrieve IODA detection and recovery transitions in an explicit Unix-second window of at most 31 days. Omit entity filters for global scope; a code requires entityType. relatedToType and relatedToCode limit results to entityType entities within one country, region, ASN, or geoasn, served at page 0 only. Each transition retains its source, level, condition, value and baseline; levels and baselines are not a source-independent severity scale. A recovery's historyValue can be a baseline IODA re-based during a long event; compare its value with the detection's historyValue and condition. Transitions include both requested bounds, widened by extendWindowSeconds; adjacent windows can duplicate boundary detections. ignoreMethods excludes source.method, source.*, or *.method upstream. Missing transitions do not establish health. Pages are zero-based; keep filters and limit fixed.

NameTypeReqDescription
entityCodestring–Two-letter country code, IODA numeric region code, decimal ASN (AS prefix accepted), or geoasn code joining an ASN and a region or country code (40934-576, 59962-IR); resolve names with ioda_search_e…
entityTypestring–country, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
extendWindowSecondsinteger–Seconds before from and after until to also return transitions from; zero, the default, returns only transitions inside the window. Without entityType, large extensions are slow globally and can time…
fromintegeryesInclusive Unix seconds UTC; no milliseconds; window at most 31 days. IODA's API holds no outage detections before 2022-01-26 UTC.
ignoreMethodsarray–Detection methods to exclude upstream before event construction and scoring; duplicates are removed, and an empty array excludes nothing. Keep fixed across ranking and drill-down calls.
limitinteger–Default 20; a larger value returns at most 1000 and says so. Keep fixed when continuing.
pageinteger–Zero-based upstream page; restart at 0 when changing limit.
relatedToCodestring–Scope entity code, normalized like entityCode for relatedToType (IR, 1829, AS42337, 60627-IR); resolve names with ioda_search_entities. Provide with relatedToType.
relatedToTypestring–Scope type: country, region, asn, or geoasn. With relatedToCode, returns entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and excludes e…
sourcestring–bgp, ping-slash24, merit-nt, or gtr; blank means all sources. Case and whitespace are normalized.
untilintegeryesInclusive Unix seconds UTC for transition/event-start selection, after from and no later than now; adjacent windows can duplicate boundary detections.
NameTypeReqDescription
alertsarray–Literal detection and recovery transitions with source baselines.
appliedobject–Every normalized input, effective window, filter and pagination value.
errorobject–Present when the call failed. Absent on success.
noticestring–Result interpretation and concrete next call.
paginationobject–Upstream page and possible continuation.
provenanceobject–Endpoint and original source attribution.
truncatedobject–A full page may have further records; not an exact total.

No examples provided.

ioda_get_signals ~482

Fetch numeric BGP visibility, active IPv4 /24 probing, Merit telescope, or Google Transparency Report traffic series for one entity in an explicit Unix-second window of at most 31 days. source is required: bgp, ping-slash24, merit-nt, or gtr (countries only). Nulls are not zero connectivity: trailing nulls in buckets not yet ended or ended within the publication allowance before the call (1800 seconds for bgp and ping-slash24, 10800 for merit-nt and gtr) are usually unpublished, and every other null is a missing observation; the notice counts each trailing class. maxPoints requests upstream aggregation, not first-N samples; smaller values lose temporal resolution. Returned series retain aligned boundary buckets with exclusive returned until bounds that may extend beyond requested bounds; timestamps and intervals support cross-source comparisons.

NameTypeReqDescription
entityCodestringyesTwo-letter country code, IODA numeric region code, decimal ASN (AS prefix accepted), or geoasn code joining an ASN and a region or country code (40934-576, 59962-IR); resolve names with ioda_search_e…
entityTypestringyescountry, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
fromintegeryesRequested start Unix seconds UTC; window at most 31 days. Aligned returned buckets may begin earlier. IODA's API holds no merit-nt observations before 2022-01-09 UTC, no bgp before 2022-01-18, and no…
maxPointsinteger–Upstream aggregation target, not a local sample cap; smaller targets lose temporal resolution. Default 200; a value above 10000 is served as 10000 and says so.
sourcestringyesExactly bgp, ping-slash24, merit-nt, or gtr; case and whitespace normalized. gtr (Google Transparency Report traffic) covers countries only; ucsd-nt is not supported.
untilintegeryesRequested end Unix seconds UTC, after from and no later than now. Returned bucket bounds are exclusive and may extend beyond this requested bound due to alignment.
NameTypeReqDescription
appliedobject–Every normalized input, effective window, filter and pagination value.
errorobject–Present when the call failed. Absent on success.
noticestring–Result interpretation and concrete next call.
provenanceobject–Endpoint and original source attribution.
semanticsobject–Source-specific measurement semantics and IODA unit.
seriesarray–All numeric subtypes and buckets, preserving nulls and aligned bounds.
truncatedobject–A full page may have further records; not an exact total.

No examples provided.

ioda_get_status ~247

Inspect recent IODA detection evidence and measurement coverage for one entity over a lookback of 1–24 hours. Collect events, alerts, bgp, ping-slash24 and merit-nt evidence. Partial failures remain explicit and route to standalone tools. recent, stale, no_data and unknown describe observation availability; buckets within the 1800-second publication allowance count as pending, not missing. No alerts is not an all-clear. IODA measures macroscopic connectivity, not one office or a shutdown cause.

NameTypeReqDescription
entityCodestringyesTwo-letter country code, IODA numeric region code, decimal ASN (AS prefix accepted), or geoasn code joining an ASN and a region or country code (40934-576, 59962-IR); resolve names with ioda_search_e…
entityTypestringyescountry, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
lookbackHoursinteger–Hours before the captured invocation time; values above 24 are served as 24 with a notice naming the uncovered earlier window. The exact window is returned.
NameTypeReqDescription
alertsobject–Successful alert component
appliedobject–Every normalized input, effective window, filter and pagination value.
asOfinteger–Captured invocation time, Unix seconds UTC
componentsarray–Five component outcomes in request order
detectionstring–Returned lookback detection evidence
entityobject–Requested entity
errorobject–Present when the call failed. Absent on success.
eventsobject–Successful event component
limitationsarray–Scope, completeness, alignment and freshness qualifications
noticestring–Result interpretation and concrete next call.
signalsarray–Coverage for each core source
truncatedobject–A full page may have further records; not an exact total.
windowobject–Exact investigation window

No examples provided.

ioda_search_entities ~514

Resolve country, region, autonomous-system, or geoasn (one ASN within a region or country) names and codes for outage investigations. Choose entityType and either query or entityCode; omit both to list the type. Countries use two letters, regions numeric IODA codes, ASNs decimal digits (AS prefix accepted), geoasns an ASN and a region or country code (40934-576, 59962-IR). Add relatedToType and relatedToCode to list entityType entities within one country, region, ASN, or geoasn, such as the regions or networks of a country; a scope combines with query. Region results can include IODA geolocation catch-alls named [Invalid Region (N)] or Unknown Region in <country>, which are not provinces or states; a notice names them. Metadata does not establish measurement coverage. Pages are zero-based; keep limit fixed when continuing.

NameTypeReqDescription
entityCodestring–Two-letter country code, IODA numeric region code, decimal ASN (AS prefix accepted), or geoasn code joining an ASN and a region or country code (40934-576, 59962-IR); resolve names with ioda_search_e…
entityTypestringyescountry, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
limitinteger–Default 20; a larger value returns at most 1000 and says so. Keep fixed when continuing.
pageinteger–Zero-based upstream page; restart at 0 when changing limit.
querystring–Case-insensitive name substring, matched literally (% and _ are not wildcards); trimmed to at most 200 UTF-16 code units, and blank is omitted. Mutually exclusive with entityCode.
relatedToCodestring–Scope entity code, normalized like entityCode for relatedToType (IR, 1829, AS42337, 60627-IR); resolve names with ioda_search_entities. Provide with relatedToType.
relatedToTypestring–Scope type: country, region, asn, or geoasn. With relatedToCode, returns entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and excludes e…
NameTypeReqDescription
appliedobject–Every normalized input, effective window, filter and pagination value.
entitiesarray–Original entity metadata; not measurement coverage.
errorobject–Present when the call failed. Absent on success.
noticestring–Result interpretation and concrete next call.
paginationobject–Upstream page and possible continuation.
provenanceobject–Endpoint and original source attribution.
truncatedobject–A full page may have further records; not an exact total.

No examples provided.

ioda_summarize_outages ~741

Rank the entities of one entityType by IODA's outage summary score over an explicit Unix-second window of at most 31 days, such as the countries or a country's regions hit hardest this week. Rows keep IODA's order, descending scores.overall. Region rankings can include IODA geolocation catch-alls named [Invalid Region (N)] or Unknown Region in <country>, which are not provinces or states; a notice names them. IODA merges overlapping events from different sources, scores each merged event as the product of its sources' scores, and sums the merged events into overall; each <source>.<method> key sums that source's event scores. Scores are window totals for ranking the rows of one request, not current status, and are not comparable across requests with different windows. Add entityCode for one entity, or relatedToType and relatedToCode to rank entityType entities within one country, region, ASN, or geoasn; large type-only rankings can time out. Event-start selection includes until, so adjacent windows can duplicate boundary detections. ignoreMethods excludes source.method, source.*, or *.method upstream before scoring; keep exclusions fixed when comparing rankings or drilling into events and alerts. An empty result is not an all-clear. Pages are zero-based; keep filters and limit fixed.

NameTypeReqDescription
entityCodestring–Two-letter country code, IODA numeric region code, decimal ASN (AS prefix accepted), or geoasn code joining an ASN and a region or country code (40934-576, 59962-IR); resolve names with ioda_search_e…
entityTypestringyescountry, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
extendWindowSecondsinteger–Seconds before from to search for the start of an event overlapping the window, and after until for its recovery; defaults to 1209600 (14 days), IODA's default. Values above 1209600 are served as 120…
fromintegeryesInclusive Unix seconds UTC; no milliseconds; window at most 31 days. IODA's API holds no outage detections before 2022-01-26 UTC.
ignoreMethodsarray–Detection methods to exclude upstream before event construction and scoring; duplicates are removed, and an empty array excludes nothing. Keep fixed across ranking and drill-down calls.
limitinteger–Default 20; a larger value returns at most 1000 and says so. Keep fixed when continuing.
pageinteger–Zero-based upstream page; restart at 0 when changing limit.
relatedToCodestring–Scope entity code, normalized like entityCode for relatedToType (IR, 1829, AS42337, 60627-IR); resolve names with ioda_search_entities. Provide with relatedToType.
relatedToTypestring–Scope type: country, region, asn, or geoasn. With relatedToCode, returns entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and excludes e…
untilintegeryesInclusive Unix seconds UTC for transition/event-start selection, after from and no later than now; adjacent windows can duplicate boundary detections.
NameTypeReqDescription
appliedobject–Every normalized input, effective window, filter and pagination value.
errorobject–Present when the call failed. Absent on success.
noticestring–Result interpretation and concrete next call.
paginationobject–Upstream page and possible continuation.
provenanceobject–Endpoint and original source attribution.
summariesarray–IODA's per-entity summaries in its own order, descending scores.overall.
truncatedobject–A full page may have further records; not an exact total.

No examples provided.

Install

How do I install the io.github.cyanheads/ioda-outages-mcp-server server?

io.github.cyanheads/ioda-outages-mcp-server is a hosted endpoint at https://ioda-outages.caseyjhand.com/mcp, 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 · ioda-outages.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-ioda-outages-mcp-server 'https://ioda-outages.caseyjhand.com/mcp'
Common questions

What is the io.github.cyanheads/ioda-outages-mcp-server server?

io.github.cyanheads/ioda-outages-mcp-server is listed in the public MCP registry as io.github.cyanheads/ioda-outages-mcp-server. Investigate Internet outages with IODA events, alerts, and connectivity signals via MCP. This page covers its hosted endpoint (https://ioda-outages.caseyjhand.com/mcp).

Is the io.github.cyanheads/ioda-outages-mcp-server server safe to use?

io.github.cyanheads/ioda-outages-mcp-server scores 79 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 io.github.cyanheads/ioda-outages-mcp-server server expose?

io.github.cyanheads/ioda-outages-mcp-server exposes 6 tools: ioda_search_entities, ioda_get_status, ioda_find_outages, ioda_summarize_outages, ioda_get_signals, ioda_get_alerts. Their descriptions and schemas cost roughly 3,382 tokens of context every time the server is loaded.

Does the io.github.cyanheads/ioda-outages-mcp-server server require authentication?

No. We connected to io.github.cyanheads/ioda-outages-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/ioda-outages-mcp-server server still maintained?

io.github.cyanheads/ioda-outages-mcp-server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.