Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Investigate Internet outages with IODA events, alerts, and connectivity signals via MCP.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
IODA_CLAMP_LIMITS, MCP_LOG_LEVELDu brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://ioda-outages.caseyjhand.com/mcpÖffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"ioda-outages": {
"command": "npx",
"args": [
"-y",
"@cyanheads/ioda-outages-mcp-server"
],
"env": {
"IODA_CLAMP_LIMITS": "your-value",
"MCP_LOG_LEVEL": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add --transport http ioda-outages https://ioda-outages.caseyjhand.com/mcpclaude mcp add ioda-outages --env IODA_CLAMP_LIMITS=your-value --env MCP_LOG_LEVEL=your-value -- npx -y @cyanheads/ioda-outages-mcp-serverTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"ioda-outages": {
"url": "https://ioda-outages.caseyjhand.com/mcp"
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"ioda-outages": {
"command": "npx",
"args": [
"-y",
"@cyanheads/ioda-outages-mcp-server"
],
"env": {
"IODA_CLAMP_LIMITS": "your-value",
"MCP_LOG_LEVEL": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"ioda-outages": {
"type": "http",
"url": "https://ioda-outages.caseyjhand.com/mcp"
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"ioda-outages": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cyanheads/ioda-outages-mcp-server"
],
"env": {
"IODA_CLAMP_LIMITS": "your-value",
"MCP_LOG_LEVEL": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://ioda-outages.caseyjhand.com/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
IODA_CLAMP_LIMITS envMCP_LOG_LEVEL envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
ioda_search_entitiesResolve 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
ioda_get_statusInspect 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 descri
ioda_find_outagesFind 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 entity
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 this week. Rows keep IODA's order, descending scores.overall. Region rankings can include IODA geolo
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 days. source is required: bgp, ping-slash24, merit-nt, or gtr (countries only). Nulls are not zero c
ioda_get_alertsRetrieve 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
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 10. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto cyanheads bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Antwort in 174 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 6 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.3.1) kam vor 8 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Beefi
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
US public company data from SEC EDGAR: financials, insider trades, 13F holdings, filings and macro.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
@cyanheads/ioda-outages-mcp-server Investigate Internet outages with IODA events, alerts, and connectivity signals via MCP. STDIO or Streamable HTTP. 6 Tools • 1 Skill
Public Hosted Server: https://ioda-outages.caseyjhand.com/mcp
Internet outage evidence from IODA, using its public v2 API. Resolve countries, regions, and autonomous systems; inspect recent detections and measurement coverage; then investigate events, alert transitions, per-entity outage rankings, and numeric signals. Runs over stdio, stateless Streamable HTTP, or the public hosted endpoint above, without an API key.
| Tool | Description |
|---|---|
ioda_search_entities | Resolve country, region, ASN, or geoasn names and codes |
ioda_get_status | Inspect recent detection evidence and coverage across three numeric sources |
ioda_find_outages | Retrieve overlapping outage events for an entity or globally |
ioda_summarize_outages | Rank the entities of one type by IODA's per-window outage score |
ioda_get_signals | Fetch BGP, active IPv4 /24 probing, Merit telescope, or country-level Google Transparency Report traffic numeric series |
ioda_get_alerts | Retrieve detection and recovery transitions with source baselines |
| Skill | Description |
|---|---|
ioda-outages-guide | Investigate Internet outages with the ioda_* tools — resolving places and networks to IODA codes, publication lag, signal resolution, and reading detections and rankings without over-claiming |
ioda_search_entities toolentityType: country | region | asn | geoasn (a geoasn is one ASN within a region or country); choose query (up to 200 UTF-16 code units after trimming, matched literally as a case-insensitive name substring) or entityCode, or omit both to list the type. Country codes use two letters, regions use IODA numeric codes, ASNs use decimal digits, and geoasns join an ASN and a region or country code (40934-576, 59962-IR).relatedToType and relatedToCode list entityType entities within one country, region, ASN, or geoasn; both or neither, entityType required, no entityCode, and a scope combines with query. Page this resolver to select codes for individual outage investigations.limit is at least 1, default 20, served at most 1,000; page starts at 0. Returns original entities, pagination, and provenance; a metadata match does not establish measurement coverage. Region pages can include IODA geolocation catch-alls named [Invalid Region (N)] or Unknown Region in ; a notice names their codes, and the rows stay as IODA returns them. An asn entityCode IODA holds no record of returns a placeholder row with attrs.ip_count "0"; a notice names it.ioda_get_status toolentityType (country, region, asn, or geoasn) and entityCode; lookbackHours is at least 1, default 6, served at most 24 with a notice naming the uncovered earlier window. Collects events, alerts, and bgp, ping-slash24, and merit-nt summaries within the returned window.detection is observed, none_returned, or unknown; source coverage is independently recent, stale, no_data, or unknown. recent means the latest completed observation ended within a 1,800-second publication allowance of the call, the same for all three sources, a server policy rather than an upstream SLA. Trailing nulls inside the allowance count as pendingCount, not nullCount.signals entry carries IODA's unit for its source (Visible /24s, Up /24s, Unique Source IPs); latest, minimum, and maximum are in that unit.components disclose partial failures and standalone-tool recovery. Event/alert pages carry continuation metadata; raw samples come from ioda_get_signals. All-component failure fails the call; an unknown country, region, or geoasn code fails with entity_not_found. IODA answers an unknown asn code with a placeholder instead; when no event, alert, or series came back for an asn, a notice says a returned ioda_search_entities row does not confirm IODA holds data for it.ioda_find_outages toolfrom and until; optional entityType (country, region, asn, or geoasn), entityCode, and source: bgp | ping-slash24 | merit-nt | gtr. Omit entity filters for global scope; a code requires its type. Optional relatedToType and relatedToCode limit results to entityType entities within one country, region, ASN, or geoasn (both or neither, entityType required, no entityCode). limit is at least 1, default 20, served at most 1,000.events, pagination, and provenance. Scores retain their source meaning; starts may precede the window and an end clipped at until does not establish recovery.includeAlerts defaults to false; extendWindowSeconds is at least 0, served at most 1,209,600. Omitted, it is 1,209,600 with entityType and 86,400 without it, because large global extensions can time out; the applied value is echoed, and a notice discloses the global default. Global searches over multi-day windows can still time out: narrow the window or add entityType. Zero extension can miss long-running detections.ioda_summarize_outages toolentityType, from, and until; optional entityCode for one entity, or relatedToType and relatedToCode to rank entityType entities within one country, region, ASN, or geoasn (both or neither, no entityCode). limit is at least 1, default 20, served at most 1,000; extendWindowSeconds is at least 0, default 1,209,600, served at most 1,209,600. There is no source input.summaries in IODA's order, descending scores.overall, with pagination and provenance. Each row carries the entity, event_cnt (IODA's count of source events before merging), and unmodified scores: overall plus one sum of event scores per . key. 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.entityCode or a related scope. Region rankings, like region events and alerts, can include the catch-all rows described above; a notice names their codes. An empty result is not an all-clear.ioda_get_signals toolentityType may be geoasn), from, until, and source: bgp | ping-slash24 | merit-nt | gtr (gtr covers countries only; ucsd-nt is not supported). maxPoints is at least 1, default 200, served at most 10,000: an upstream aggregation target, not a hard returned-sample cap.series, source-specific semantics (measurement, IODA's unit, caveat; gtr reads Traffic, to compare a country with its own history), and provenance. An unknown country, region, or geoasn code fails with entity_not_found. Returned until is an exclusive bucket bound; alignment can extend beyond requested bounds. Coarse series carry a notice: values need not equal an unweighted mean of finer returned buckets, and non-null aggregates cannot establish complete finer-resolution coverage. Values, nulls, and units remain unchanged; status coverage stays unknown for coarse series.bgp and ping-slash24, 10,800 for merit-nt and gtr), or missing; the first two are usually unpublished, so end the window at least the allowance plus one bucket step before the call, since the last returned bucket can end after until. A coarse last non-null bucket inside the allowance can aggregate only the samples published so far. Interior nulls stay missing observations.series gets a notice by case: gtr for a region, ASN, or geoasn (it covers countries only); a window ending by the source's archive start, which says IODA holds nothing earlier instead of suggesting another code or window; a window starting inside the publication allowance, which IODA may not have published yet; an asn, where a returned search row does not confirm data and attrs.ip_count "0" marks IODA's placeholder.ioda_get_alerts toolfrom and until; optional entity, source, and related-scope filters match ioda_find_outages; a related scope is served at page 0 only, because IODA cannot continue scoped alerts. limit is at least 1, default 20, served at most 1,000; extendWindowSeconds is at least 0, default 0, served at most 1,209,600.alerts, pagination, and provenance, retaining source level, condition, value, and historyValue when reported. value and historyValue are in the source unit for bgp, ping-slash24, and merit-nt; for gtr they are IODA Traffic divided by 1,000,000 and truncated. 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. A missing transition does not establish health or rule out an event that began earlier.ioda-outages-guide skillasn versusNur der Anfang wird gezeigt; den Rest findest du im Repo