# io.github.cyanheads/ioda-outages-mcp-server (remote · ioda-outages.caseyjhand.com)

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

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ioda-outages.caseyjhand.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/ioda-outages.md), [page](https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/ioda-outages)
- npm · `@cyanheads/ioda-outages-mcp-server`: 39/100, [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

- Endpoint: `https://ioda-outages.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

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

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 8 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).

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

### Claude

```bash
claude mcp add --transport http cyanheads-ioda-outages-mcp-server 'https://ioda-outages.caseyjhand.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cyanheads-ioda-outages-mcp-server": {
      "url": "https://ioda-outages.caseyjhand.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cyanheads-ioda-outages-mcp-server": {
      "type": "http",
      "url": "https://ioda-outages.caseyjhand.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cyanheads-ioda-outages-mcp-server]
url = "https://ioda-outages.caseyjhand.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-ioda-outages-mcp-server": {
      "type": "remote",
      "url": "https://ioda-outages.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyanheads-ioda-outages-mcp-server --url 'https://ioda-outages.caseyjhand.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyanheads-ioda-outages-mcp-server:
    url: "https://ioda-outages.caseyjhand.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cyanheads-ioda-outages-mcp-server": {
      "Transport": "http",
      "Url": "https://ioda-outages.caseyjhand.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cyanheads-ioda-outages-mcp-server -t streamable-http -u 'https://ioda-outages.caseyjhand.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cyanheads-ioda-outages-mcp-server": {
      "type": "http",
      "url": "https://ioda-outages.caseyjhand.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 80, +1)

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

### 2026-11-03 (score 79, +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.

### 2026-11-01 (score 78, +1)

- [security] The server rewrote its instructions, which are the text every model session 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] Tool “ioda_get_signals” rewrote its description, which is the text the model reads
- [functional] Schema quality: good → excellent
- [functional] Server version: 0.3.0 → 0.3.1
- [cosmetic] “ioda_find_outages” reworded the description of “from”
- [cosmetic] “ioda_get_alerts” reworded the description of “limit”
- [cosmetic] “ioda_get_alerts” reworded the description of “from”
- [cosmetic] “ioda_find_outages” 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”

### 2026-10-30 (score 77, +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.

### 2026-10-29 (score 76, +3)

- [functional improvement] 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

### 2026-10-27 (score 73, +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.

### 2026-10-25 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 71)

First indexed and scored.

## MCP tools (6)

### `ioda_search_entities` (~514 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. 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.

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): Default 20; a larger value returns at most 1000 and says so. Keep fixed when continuing.
- `page` (integer): Zero-based upstream page; restart at 0 when changing limit.
- `query` (string): 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.
- `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 entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and excludes e…

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` (~718 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 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.

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. IODA's API holds no outage detections before 2022-01-26 UTC.
- `ignoreMethods` (array): 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.
- `includeAlerts` (boolean): Include original nested alert transitions and baselines; may substantially increase response size.
- `limit` (integer): Default 20; a larger value returns at most 1000 and says so. 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 entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and excludes e…
- `source` (string): bgp, ping-slash24, merit-nt, or gtr; blank means all sources. Case and whitespace are normalized.
- `until` (integer, required): Inclusive Unix seconds UTC for transition/event-start selection, after from and no later than now; adjacent windows can duplicate boundary detections.

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` (~741 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. 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.

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. IODA's API holds no outage detections before 2022-01-26 UTC.
- `ignoreMethods` (array): 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.
- `limit` (integer): Default 20; a larger value returns at most 1000 and says so. 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 entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and excludes e…
- `until` (integer, required): Inclusive Unix seconds UTC for transition/event-start selection, after from and no later than now; adjacent windows can duplicate boundary detections.

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` (~482 tokens)

Ioda Get Signals

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.

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): Requested 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…
- `maxPoints` (integer): 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.
- `source` (string, required): Exactly bgp, ping-slash24, merit-nt, or gtr; case and whitespace normalized. gtr (Google Transparency Report traffic) covers countries only; ucsd-nt is not supported.
- `until` (integer, required): Requested 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.

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` (~680 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. 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.

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. IODA's API holds no outage detections before 2022-01-26 UTC.
- `ignoreMethods` (array): 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.
- `limit` (integer): Default 20; a larger value returns at most 1000 and says so. 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 entityType entities related to that entity, such as the regions or networks of one country. Requires entityType and excludes e…
- `source` (string): bgp, ping-slash24, merit-nt, or gtr; blank means all sources. Case and whitespace are normalized.
- `until` (integer, required): Inclusive Unix seconds UTC for transition/event-start selection, after from and no later than now; adjacent windows can duplicate boundary detections.

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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/ioda-outages#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 71

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

## Links

- Remote endpoint: https://ioda-outages.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/ioda-outages-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/ioda-outages.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/ioda-outages.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-ioda-outages-mcp-server/ioda-outages