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

NPM · @CYANHEADS/IODA-OUTAGES-MCP-SERVER

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

67 Trust /100

Last scanned (7 hours ago)

Scores higher than 38% of npm servers

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 11 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3101 tokens (~516/item across 6 items; 6 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 7 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 22 Oct 26 +25
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.87 ▲ functional
  • 21 Oct 26 42

    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 23 Oct 2026 · Analysed npm/@cyanheads/ioda-outages-mcp-server@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 36 packages
Packages resolved 36
Stale 11
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~2,819 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 ~629

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 may precede from; ends can be clipped at until and do not establish recovery. 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.
includeAlertsboolean–Include original nested alert transitions and baselines; may substantially increase response size.
limitinteger–Upstream page size; values above 100 are served as 100 with a notice. 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 only entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and exclu…
sourcestring–bgp, ping-slash24, merit-nt, or gtr; blank means all sources. Case and whitespace are normalized.
untilintegeryesExclusive Unix seconds UTC, after from and no later than now.
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 ~556

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. 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.
limitinteger–Upstream page size; values above 100 are served as 100 with a notice. 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 only entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and exclu…
sourcestring–bgp, ping-slash24, merit-nt, or gtr; blank means all sources. Case and whitespace are normalized.
untilintegeryesExclusive Unix seconds UTC, after from and no later than now.
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 ~317

Fetch numeric BGP visibility, active IPv4 /24 probing, or Merit telescope series for one entity in an explicit Unix-second window of at most 31 days. source is required: bgp, ping-slash24, or merit-nt. Nulls are missing observations, not zero connectivity. maxPoints requests upstream aggregation, not first-N samples; smaller values lose temporal resolution. Returned series retain aligned boundary buckets; 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.
fromintegeryesInclusive Unix seconds UTC; no milliseconds; window at most 31 days.
maxPointsinteger–Upstream aggregation target, not a local sample cap; smaller targets lose temporal resolution. Values above 2000 are served as 2000 with a notice.
sourcestringyesExactly bgp, ping-slash24, or merit-nt; case and whitespace normalized. gtr and ucsd-nt are not supported numeric sources.
untilintegeryesExclusive Unix seconds UTC, after from and no later than now.
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 ~469

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. 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–Upstream page size; values above 100 are served as 100 with a notice. Keep fixed when continuing.
pageinteger–Zero-based upstream page; restart at 0 when changing limit.
querystring–Name substring, trimmed to at most 200 characters; 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 only entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and exclu…
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 ~601

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. 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. 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.
limitinteger–Upstream page size; values above 100 are served as 100 with a notice. 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 only entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and exclu…
untilintegeryesExclusive Unix seconds UTC, after from and no later than now.
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 runs locally as an npm package, launched with npx -y @cyanheads/ioda-outages-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @cyanheads/ioda-outages-mcp-server

# add to Claude Code
claude mcp add cyanheads-ioda-outages-mcp-server -- npx -y @cyanheads/ioda-outages-mcp-server
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 npm package (@cyanheads/ioda-outages-mcp-server).

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

io.github.cyanheads/ioda-outages-mcp-server scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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 2,819 tokens of context every time the server is loaded.

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 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

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

io.github.cyanheads/ioda-outages-mcp-server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.