Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
Déduit des transports déclarés par cette annonce (streamable-http). Un client absent de cette liste n’est pas écarté pour autant — c’est simplement quelque chose que Forge ne peut pas confirmer.
La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.
Lu depuis un véritable échange MCP initialize → tools/list contre l’endpoint déclaré. Aucun outil n’a été invoqué — tools/list est l’appel d’introspection en lecture seule que le protocole prévoit pour cela. Cela reflète ce que le serveur annonçait à cet instant ; un endpoint hébergé n’est figé sur aucune version et peut changer sans préavis.
https://outagedeck.com/api/mcp14 outils · 149 msget_provider_statusLive status for one tracked provider: overall state, non-operational services, and open incidents, read from the vendor's official status feed. Accepts a slug, provider name, or product name (e.g., "claude" resolves to Anthropic). Use this first for any "is X down?" question.Live status for one tracked provider: overall state, non-operational services, and open incidents, read from the vendor's official status feed. Accepts a slug, provider name, or product name (e.g., "claude" resolves to Anthropic). Use this first for any "is X down?" question.
| Paramètre | Type | Description |
|---|---|---|
| provider* | string | Provider slug, name, or product name, e.g., "aws", "GitHub", "chatgpt". |
check_my_stackOne verdict across up to 12 providers: whether any vendor in the list is reported as having a problem right now. Use before debugging an integration failure to answer "is it us or them?" in a single call. Returns a shareable status-board link and a prefilled alert setup link.One verdict across up to 12 providers: whether any vendor in the list is reported as having a problem right now. Use before debugging an integration failure to answer "is it us or them?" in a single call. Returns a shareable status-board link and a prefilled alert setup link.
| Paramètre | Type | Description |
|---|---|---|
| providers* | array | Provider slugs, names, or product names, one per vendor the stack depends on. |
list_active_incidentsEvery incident currently open across all tracked providers, most severe first. Optionally filter by severity (critical, major, minor, maintenance). Use to answer "what is down right now?" across the whole cloud landscape.Every incident currently open across all tracked providers, most severe first. Optionally filter by severity (critical, major, minor, maintenance). Use to answer "what is down right now?" across the whole cloud landscape.
| Paramètre | Type | Description |
|---|---|---|
| severity | string | Only incidents of this severity. |
get_incident_detailsFull detail for one incident: updates from the official incident source in chronological order, the services OutageDeck matched to it, severity, and resolution state. Pass the incident slug returned by list_active_incidents or get_provider_status. Use to read what the official source has actually s…Full detail for one incident: updates from the official incident source in chronological order, the services OutageDeck matched to it, severity, and resolution state. Pass the incident slug returned by list_active_incidents or get_provider_status. Use to read what the official source has actually s…
| Paramètre | Type | Description |
|---|---|---|
| incident* | string | Incident slug, e.g., from an earlier list_active_incidents result. |
get_uptimeIndependent uptime record for one provider over a trailing window (7-90 days, default 30), computed from OutageDeck's own observations of the vendor's official feed: share of time free of major outages, strict uptime with partial outages counted as downtime, and total impaired durations.Independent uptime record for one provider over a trailing window (7-90 days, default 30), computed from OutageDeck's own observations of the vendor's official feed: share of time free of major outages, strict uptime with partial outages counted as downtime, and total impaired durations.
| Paramètre | Type | Description |
|---|---|---|
| provider* | string | Provider slug, name, or product name. |
| days | integer | Trailing window in days (default 30). |
get_outage_reportA reliability summary across every tracked provider over a trailing window (7-90 days, default 30): incident totals, severity and category breakdowns, the providers hit hardest by major outages, and the longest-running severe incidents. Use to answer "which vendors had outages recently?" or to comp…A reliability summary across every tracked provider over a trailing window (7-90 days, default 30): incident totals, severity and category breakdowns, the providers hit hardest by major outages, and the longest-running severe incidents. Use to answer "which vendors had outages recently?" or to comp…
| Paramètre | Type | Description |
|---|---|---|
| days | integer | Trailing window in days (default 30). |
search_providersFind tracked providers by name, product name, or fragment ("postgres", "auth", "claude"). Returns slugs to use with the other tools plus each match's current status. Use when a provider argument did not resolve or to discover what OutageDeck tracks.Find tracked providers by name, product name, or fragment ("postgres", "auth", "claude"). Returns slugs to use with the other tools plus each match's current status. Use when a provider argument did not resolve or to discover what OutageDeck tracks.
| Paramètre | Type | Description |
|---|---|---|
| query* | string | Free-text search over provider names and aliases. |
list_custom_providersLists the custom providers on the caller's own OutageDeck account: vendors they registered themselves by pointing at a status feed we do not track in the public catalog. Requires an API key, and only ever returns that key owner's providers.Lists the custom providers on the caller's own OutageDeck account: vendors they registered themselves by pointing at a status feed we do not track in the public catalog. Requires an API key, and only ever returns that key owner's providers.
Aucun schéma d’entrée n’a été publié pour cet outil.
add_custom_providerRegisters a vendor OutageDeck does not track by pointing at its Statuspage or Instatus status page, so it joins the caller's account with live status, incident history, and alerting. Requires an API key and a plan that includes custom providers. The feed is read live before anything is saved, and i…Registers a vendor OutageDeck does not track by pointing at its Statuspage or Instatus status page, so it joins the caller's account with live status, incident history, and alerting. Requires an API key and a plan that includes custom providers. The feed is read live before anything is saved, and i…
url : Links to undeclared domain: status.yourvendor.com| Paramètre | Type | Description |
|---|---|---|
| url* | string | The vendor's status page address, for example https://status.yourvendor.com. |
| name | string | Optional display name. Defaults to the name the status page publishes. |
update_custom_providerRenames one of the caller's custom providers, points it at a different status page, or pauses and resumes its checks. Requires an API key. A new address is read live before it is stored.Renames one of the caller's custom providers, points it at a different status page, or pauses and resumes its checks. Requires an API key. A new address is read live before it is stored.
| Paramètre | Type | Description |
|---|---|---|
| provider* | string | The custom provider's name or id. |
| name | string | New display name. |
| url | string | New status page address. |
| state | string | Resume or pause its checks, which run about every 10 minutes. |
remove_custom_providerprivilégiéDeletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.
| Paramètre | Type | Description |
|---|---|---|
| provider* | string | The custom provider's name or id. |
watch_providerStarts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. Alerts are emailed to the account address; the other channels (Slack, Teams, Discord, webhook) are set up on the account page, so no webhook URL ever ha…Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. Alerts are emailed to the account address; the other channels (Slack, Teams, Discord, webhook) are set up on the account page, so no webhook URL ever ha…
| Paramètre | Type | Description |
|---|---|---|
| provider* | string | A tracked provider (slug, name, or product name) or one of the caller's own custom providers. |
searchSearch everything OutageDeck tracks: cloud and SaaS providers, and their incident history. Returns citable results with stable ids for the fetch tool. Use for open questions like "who had outages last week" or "find the GitHub Actions incident"; use get_provider_status when the question is simply w…Search everything OutageDeck tracks: cloud and SaaS providers, and their incident history. Returns citable results with stable ids for the fetch tool. Use for open questions like "who had outages last week" or "find the GitHub Actions incident"; use get_provider_status when the question is simply w…
| Paramètre | Type | Description |
|---|---|---|
| query* | string | What to look for: a vendor name, a product, or words from an incident title, e.g., "cloudflare", "elevated error rates". |
fetchRetrieve the full text of one search result by its id: a provider's current status with its services and open incidents, or an incident's complete timeline. Ids come from the search tool.Retrieve the full text of one search result by its id: a provider's current status with its services and open incidents, or an incident's complete timeline. Ids come from the search tool.
| Paramètre | Type | Description |
|---|---|---|
| id* | string | A document id returned by search, e.g., "provider:aws" or "incident:github-actions-delays-2026-07-31". |
14 outils sur 14 ont publié une description.
Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.
Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
Les noms cliquables ouvrent l’index Forge de toutes les entrées observées exposant cet outil. Parcourir tous les outils indexés.
Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.