ioda-outages-mcp-server
io.github.cyanheads/ioda-outages-mcp-servercyanheadsstreamable-httpv0.3.2Scanned
Investigate Internet outages with IODA events, alerts, and connectivity signals via MCP.
6 tools: 6 only read.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ioda-outages-mcp-server can do
The ioda-outages-mcp-server is published by the GitHub account cyanheads. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
6 tools bring in text other people can write (ioda_search_entities, ioda_get_status, ioda_find_outages and 3 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 0.3.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Only reads 6Show 6 read-only tools
ioda_find_outagesFind IODA outage events overlapping an explicit Unix-second window of at most 31 days.Reads text others writeNo findings
Why it is in this group
- The name "ioda_find_outages" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Events default to oldest start first. Use source with score_desc because scores from different sources use different scales. 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, order, and limit fixed.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
ioda_get_alertsRetrieve IODA detection and recovery transitions in an explicit Unix-second window of at most 31 days.Reads text others writeNo findings
Why it is in this group
- The name "ioda_get_alerts" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
ioda_get_signalsFetch 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 …Reads text others writeNo findings
Why it is in this group
- The name "ioda_get_signals" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
ioda_get_statusInspect recent IODA detection evidence and measurement coverage for one entity over a lookback of 1–24 hours.Reads text others writeNo findings
Why it is in this group
- The name "ioda_get_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Completed trailing nulls count as pending when they ended within the source's publication allowance of the call (1800 seconds for bgp and ping-slash24, 10800 for merit-nt). No alerts is not an all-clear. IODA measures macroscopic connectivity, not one office or a shutdown cause.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
ioda_search_entitiesResolve country, region, autonomous-system, or geoasn (one ASN within a region or country) names and codes for outage investigations.Reads text others writeNo findings
Why it is in this group
- The name "ioda_search_entities" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
ioda_summarize_outagesRank 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 …Reads text others writeNo findings
Why it is in this group
- The name "ioda_summarize_outages" says "summarize": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:23 UTC, unchanged since Oct 25, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:ioda_find_outagesOnly readsdescriptioninputSchema
- Changed:ioda_get_alertsOnly readsinputSchema
- Changed:ioda_get_statusOnly readsdescription
- Changed:ioda_summarize_outagesOnly readsinputSchema
Tools6 changed.~6 changedView diff
- Changed:ioda_find_outagesOnly readsinputSchema
- Changed:ioda_get_alertsOnly readsdescriptioninputSchema
- Changed:ioda_get_signalsOnly readsdescriptioninputSchema
- Changed:ioda_get_statusOnly readsinputSchema
- Changed:ioda_search_entitiesOnly readsdescriptioninputSchema
- Changed:ioda_summarize_outagesOnly readsdescriptioninputSchema
Install
Pinned to version 0.3.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http ioda-outages https://ioda-outages.caseyjhand.com/mcpclaude mcp add --transport http ioda-outages https://ioda-outages.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ioda-outages__ioda_search_entities",
"mcp__ioda-outages__ioda_get_status",
"mcp__ioda-outages__ioda_find_outages",
"mcp__ioda-outages__ioda_summarize_outages",
"mcp__ioda-outages__ioda_get_signals",
"mcp__ioda-outages__ioda_get_alerts"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ioda-outages. Review it before you use it.
Capability tags behind 6 rules
- mcp__ioda-outages__ioda_search_entities untrusted-input
- mcp__ioda-outages__ioda_get_status untrusted-input
- mcp__ioda-outages__ioda_find_outages untrusted-input
- mcp__ioda-outages__ioda_summarize_outages untrusted-input
- mcp__ioda-outages__ioda_get_signals untrusted-input
- mcp__ioda-outages__ioda_get_alerts untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/ioda-outages-mcp-server/verify?hash=71fdb07be27badd87fe9d366de46f8c8e9c3dbf3f86fb3229842d1d891844ec0" | jq -e '.changed == false'Pinned hash 71fdb07be27b, from Nov 21, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/ioda-outages-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/ioda-outages-mcp-server)Source: MCP Registry · repository. Synced Nov 21, 2026, 17:17 UTC.
ioda-outages-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ioda-outages-mcp-server safe?
- No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the ioda-outages-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ioda-outages-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ioda-outages-mcp-server have?
- 6 tools: 6 read. ioda_search_entities, ioda_get_status, ioda_find_outages, ioda_summarize_outages, ioda_get_signals and ioda_get_alerts.
Does the ioda-outages-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ioda-outages-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ioda-outages-mcp-server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.