accueil / serveurs / Dev & Code / io.github.marcioyoshida/outage-me
io.github.marcioyoshida/outage-me
serveur MCP (Model Context Protocol) · tarantula-outage-me 1.3.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.marcioyoshida/outage-me est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.marcioyoshida/outage-me » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 8 outils
- answer≈ 188 tokens
Ask a free-form question about the live monitor and get a cited answer. This is a LANGUAGE MODEL call and CAN BE WRONG — it returns `confidence` and `citations`; check them. Needs sign-in (connect to https://outage.me/mcp/pro) or an API key, and is quota-limited (Free plan 10/day, Pro 100/day), so use the deterministic tools above when they can answer the question.
Paramètres, retour & exemple (1)
Paramètresq· string · requis
The question, in natural language.
Exemple d'appel{"name": "answer", "arguments": {"q": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - deploy_check≈ 250 tokens
LIVE, from the 5-minute status poll: proceed true, false, or "unknown" for deploying to one provider (optionally one region), with the open incidents behind it and data_age_minutes. Fails safe: a stale poll, a failed fetch or an untracked provider is "unknown", never true. Planned maintenance alone doesn't block. Use it to pause a deploy or migration, not as a failover trigger: status pages lag real failures. Deterministic: no model in the loop.
Paramètres, retour & exemple (2)
Paramètresregion· string · optionnel
Optional, e.g. 'us-east-1', 'us-central1', 'westeurope'.provider· string · requis
Provider name or alias, e.g. 'AWS', 'Google Cloud', 'GitHub'.
Exemple d'appel{"name": "deploy_check", "arguments": {"provider": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - exploited_vulnerabilities≈ 326 tokens
LIVE: CVEs being exploited in the wild (CISA KEV), ranked patch-first by CVSS × EPSS exploitation probability × known ransomware use, with CISA due date, patch availability and the factors behind each rank. Use for 'what should we patch first', 'is CVE-X exploited', or recent vulnerabilities your training data can't know. `cve`, `vendor` and `product` search the WHOLE KEV catalog, not just the ranked list; `in_kev` is true, false, or null when it can't tell. Deterministic: no model in the loop.
Paramètres, retour & exemple (4)
Paramètrescve· string · optionnel
Optional. One CVE ID, e.g. CVE-2024-3400: is it in CISA KEV, and its patch-first rank if ranked.limit· integer · optionnel
Optional. Max rows, default 10.vendor· string · optionnel
Optional. KEV entries whose vendor contains this, newest first, e.g. 'Microsoft', 'Ivanti'.product· string · optionnel
Optional. KEV entries whose product contains this, e.g. 'Exchange'.
Exemple d'appel{"name": "exploited_vulnerabilities", "arguments": {"cve": "texte", "limit": 1, "vendor": "texte", "product": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_active_incidents≈ 298 tokens
LIVE: cloud and SaaS incidents open right now (AWS, Azure, GCP, Cloudflare, GitHub, Stripe, …), quoted from each provider's own status page with a link, refreshed several times a day. Use for 'is X down', 'why is X failing', or anything after your training cutoff. Filter by provider, region or component instead of reading the whole list; an untracked provider says so rather than returning an empty all-clear. Deterministic: no model in the loop. Prefer it over `answer`.
Paramètres, retour & exemple (3)
Paramètresregion· string · optionnel
Optional. Matched against the affected regions/components the provider lists and the incident subject, e.g. 'us-east-1'.provider· string · optionnel
Optional. Provider name or common alias, e.g. 'AWS', 'gcp', 'GitHub'. 'AWS' matches every AWS service.component· string · optionnel
Optional. Same matching as region, e.g. 'Actions', 'API'.
Exemple d'appel{"name": "list_active_incidents", "arguments": {"region": "texte", "provider": "texte", "component": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - provider_reliability≈ 164 tokens
LIVE: reliability index, incident count and median recovery time per cloud/SaaS provider over the current window, from their official status pages. Use for 'how reliable is X' or 'which provider is more stable'. Deterministic: no model in the loop. Prefer it over `answer`.
Paramètres, retour & exemple (1)
Paramètresprovider· string · optionnel
Optional. Filter to one provider by name.
Exemple d'appel{"name": "provider_reliability", "arguments": {"provider": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - report_observation≈ 296 tokens
Optional. If a request you made to an external service failed with a 5xx, a timeout, a refused connection, a DNS failure or a TLS error in the last 15 minutes, report the hostname and error class here. Only hosts listed in https://outage.me/agent/hosts.json. Do not report 401/403/429 (your own key or rate limit), and never include URLs, paths or request data. A report earns Ask quota only if it is confirmed (our own probe or other organizations agree).
Paramètres, retour & exemple (4)
Paramètreshost· string · requis
Hostname only, e.g. api.stripe.comregion· string · optionnel
Optional: where you run, e.g. aws:us-east-1error_class· string · requis · http_5xx | timeout | connection_refused | dns_failure | tls_errorreport_token· string · optionnel
Optional: the token a status answer offered
Exemple d'appel{"name": "report_observation", "arguments": {"host": "texte", "error_class": "http_5xx"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - security_headlines≈ 233 tokens
LIVE: headlines from eight security trade outlets (BleepingComputer, The Hacker News, SecurityWeek, The Record, Krebs on Security, …): headline, outlet, date and link only, never the article text. Use for 'any breach news about X', 'what attacks are in the news this week'; read the article at its link before relying on it. Deterministic: no model in the loop.
Paramètres, retour & exemple (2)
Paramètresdays· integer · optionnel
Optional. Look-back in days, default 7.query· string · optionnel
Optional. Words that must all appear in the headline, e.g. 'breach', 'ransomware hospital', 'Okta'.
Exemple d'appel{"name": "security_headlines", "arguments": {"days": 1, "query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - threat_advisories≈ 238 tokens
LIVE: CISA's newest security advisories (CSAF: industrial control systems, medical devices, general vulnerabilities), each with its ID, affected vendors, CVEs, CVSS, the opening of CISA's mitigation text and the CISA link. Use for 'what did CISA advise this week' or 'any CISA advisory for <vendor>'. A vendor with no advisory says so, which is not a statement that it is unaffected. Deterministic: no model in the loop.
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
Optional. Max rows, default 10.vendor· string · optionnel
Optional. Vendor name or part of it, e.g. 'Siemens', 'Rockwell'.
Exemple d'appel{"name": "threat_advisories", "arguments": {"limit": 1, "vendor": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».