# 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.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- npm · `@cyanheads/ioda-outages-mcp-server`: 67/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/cyanheads-ioda-outages-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/cyanheads-ioda-outages-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@cyanheads/ioda-outages-mcp-server`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 11 of 36 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## 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.

### Claude

```bash
claude mcp add cyanheads-ioda-outages-mcp-server -- npx -y @cyanheads/ioda-outages-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "cyanheads-ioda-outages-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/ioda-outages-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cyanheads-ioda-outages-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/ioda-outages-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cyanheads-ioda-outages-mcp-server -- npx -y @cyanheads/ioda-outages-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-ioda-outages-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cyanheads/ioda-outages-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyanheads-ioda-outages-mcp-server --command npx --arg -y --arg @cyanheads/ioda-outages-mcp-server
```

### Hermes

```yaml
mcp_servers:
  cyanheads-ioda-outages-mcp-server:
    command: "npx"
    args: ["-y", "@cyanheads/ioda-outages-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "cyanheads-ioda-outages-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@cyanheads/ioda-outages-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cyanheads-ioda-outages-mcp-server -t stdio -c npx -a -y @cyanheads/ioda-outages-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "cyanheads-ioda-outages-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/ioda-outages-mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 67, +25)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.87

### 2026-10-21 (score 42)

First indexed and scored.

## MCP tools (6)

### `ioda_search_entities` (~469 tokens)

Ioda Search Entities

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.

Input parameters:

- `entityCode` (string): 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…
- `entityType` (string, required): country, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
- `limit` (integer): Upstream page size; values above 100 are served as 100 with a notice. Keep fixed when continuing.
- `page` (integer): Zero-based upstream page; restart at 0 when changing limit.
- `query` (string): Name substring, trimmed to at most 200 characters; blank is omitted. Mutually exclusive with entityCode.
- `relatedToCode` (string): Scope entity code, normalized like entityCode for relatedToType (IR, 1829, AS42337, 60627-IR); resolve names with ioda_search_entities. Provide with relatedToType.
- `relatedToType` (string): 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…

Output parameters:

- `applied` (object): Every normalized input, effective window, filter and pagination value.
- `entities` (array): Original entity metadata; not measurement coverage.
- `error` (object): Present when the call failed. Absent on success.
- `notice` (string): Result interpretation and concrete next call.
- `pagination` (object): Upstream page and possible continuation.
- `provenance` (object): Endpoint and original source attribution.
- `truncated` (object): A full page may have further records; not an exact total.

### `ioda_get_status` (~247 tokens)

Ioda Get Status

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.

Input parameters:

- `entityCode` (string, required): 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…
- `entityType` (string, required): country, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
- `lookbackHours` (integer): 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.

Output parameters:

- `alerts` (object): Successful alert component
- `applied` (object): Every normalized input, effective window, filter and pagination value.
- `asOf` (integer): Captured invocation time, Unix seconds UTC
- `components` (array): Five component outcomes in request order
- `detection` (string): Returned lookback detection evidence
- `entity` (object): Requested entity
- `error` (object): Present when the call failed. Absent on success.
- `events` (object): Successful event component
- `limitations` (array): Scope, completeness, alignment and freshness qualifications
- `notice` (string): Result interpretation and concrete next call.
- `signals` (array): Coverage for each core source
- `truncated` (object): A full page may have further records; not an exact total.
- `window` (object): Exact investigation window

### `ioda_find_outages` (~629 tokens)

Ioda Find Outages

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.

Input parameters:

- `entityCode` (string): 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…
- `entityType` (string): country, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
- `extendWindowSeconds` (integer): 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…
- `from` (integer, required): Inclusive Unix seconds UTC; no milliseconds; window at most 31 days.
- `includeAlerts` (boolean): Include original nested alert transitions and baselines; may substantially increase response size.
- `limit` (integer): Upstream page size; values above 100 are served as 100 with a notice. Keep fixed when continuing.
- `page` (integer): Zero-based upstream page; restart at 0 when changing limit.
- `relatedToCode` (string): Scope entity code, normalized like entityCode for relatedToType (IR, 1829, AS42337, 60627-IR); resolve names with ioda_search_entities. Provide with relatedToType.
- `relatedToType` (string): 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…
- `source` (string): bgp, ping-slash24, merit-nt, or gtr; blank means all sources. Case and whitespace are normalized.
- `until` (integer, required): Exclusive Unix seconds UTC, after from and no later than now.

Output parameters:

- `applied` (object): Every normalized input, effective window, filter and pagination value.
- `error` (object): Present when the call failed. Absent on success.
- `events` (array): Original outage events and source scores without merging or ranking.
- `notice` (string): Result interpretation and concrete next call.
- `pagination` (object): Upstream page and possible continuation.
- `provenance` (object): Endpoint and original source attribution.
- `truncated` (object): A full page may have further records; not an exact total.

### `ioda_summarize_outages` (~601 tokens)

Ioda Summarize Outages

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.

Input parameters:

- `entityCode` (string): 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…
- `entityType` (string, required): country, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
- `extendWindowSeconds` (integer): 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…
- `from` (integer, required): Inclusive Unix seconds UTC; no milliseconds; window at most 31 days.
- `limit` (integer): Upstream page size; values above 100 are served as 100 with a notice. Keep fixed when continuing.
- `page` (integer): Zero-based upstream page; restart at 0 when changing limit.
- `relatedToCode` (string): Scope entity code, normalized like entityCode for relatedToType (IR, 1829, AS42337, 60627-IR); resolve names with ioda_search_entities. Provide with relatedToType.
- `relatedToType` (string): 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…
- `until` (integer, required): Exclusive Unix seconds UTC, after from and no later than now.

Output parameters:

- `applied` (object): Every normalized input, effective window, filter and pagination value.
- `error` (object): Present when the call failed. Absent on success.
- `notice` (string): Result interpretation and concrete next call.
- `pagination` (object): Upstream page and possible continuation.
- `provenance` (object): Endpoint and original source attribution.
- `summaries` (array): IODA's per-entity summaries in its own order, descending scores.overall.
- `truncated` (object): A full page may have further records; not an exact total.

### `ioda_get_signals` (~317 tokens)

Ioda Get Signals

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.

Input parameters:

- `entityCode` (string, required): 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…
- `entityType` (string, required): country, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
- `from` (integer, required): Inclusive Unix seconds UTC; no milliseconds; window at most 31 days.
- `maxPoints` (integer): Upstream aggregation target, not a local sample cap; smaller targets lose temporal resolution. Values above 2000 are served as 2000 with a notice.
- `source` (string, required): Exactly bgp, ping-slash24, or merit-nt; case and whitespace normalized. gtr and ucsd-nt are not supported numeric sources.
- `until` (integer, required): Exclusive Unix seconds UTC, after from and no later than now.

Output parameters:

- `applied` (object): Every normalized input, effective window, filter and pagination value.
- `error` (object): Present when the call failed. Absent on success.
- `notice` (string): Result interpretation and concrete next call.
- `provenance` (object): Endpoint and original source attribution.
- `semantics` (object): Source-specific measurement semantics and IODA unit.
- `series` (array): All numeric subtypes and buckets, preserving nulls and aligned bounds.
- `truncated` (object): A full page may have further records; not an exact total.

### `ioda_get_alerts` (~556 tokens)

Ioda Get Alerts

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.

Input parameters:

- `entityCode` (string): 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…
- `entityType` (string): country, region, asn, or geoasn (one ASN within a region or country); whitespace and case are normalized.
- `extendWindowSeconds` (integer): 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…
- `from` (integer, required): Inclusive Unix seconds UTC; no milliseconds; window at most 31 days.
- `limit` (integer): Upstream page size; values above 100 are served as 100 with a notice. Keep fixed when continuing.
- `page` (integer): Zero-based upstream page; restart at 0 when changing limit.
- `relatedToCode` (string): Scope entity code, normalized like entityCode for relatedToType (IR, 1829, AS42337, 60627-IR); resolve names with ioda_search_entities. Provide with relatedToType.
- `relatedToType` (string): 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…
- `source` (string): bgp, ping-slash24, merit-nt, or gtr; blank means all sources. Case and whitespace are normalized.
- `until` (integer, required): Exclusive Unix seconds UTC, after from and no later than now.

Output parameters:

- `alerts` (array): Literal detection and recovery transitions with source baselines.
- `applied` (object): Every normalized input, effective window, filter and pagination value.
- `error` (object): Present when the call failed. Absent on success.
- `notice` (string): Result interpretation and concrete next call.
- `pagination` (object): Upstream page and possible continuation.
- `provenance` (object): Endpoint and original source attribution.
- `truncated` (object): A full page may have further records; not an exact total.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/cyanheads-ioda-outages-mcp-server#diagnostics

## Score history

- 2026-10-23: 67
- 2026-10-22: 67
- 2026-10-21: 42

## 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.

## Links

- npm package: https://www.npmjs.com/package/@cyanheads/ioda-outages-mcp-server
- Socket report: https://socket.dev/npm/package/@cyanheads/ioda-outages-mcp-server
- Repository: https://github.com/cyanheads/ioda-outages-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/cyanheads-ioda-outages-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/cyanheads-ioda-outages-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/cyanheads-ioda-outages-mcp-server
