Add OutageDeck remote MCP server

[koko3tallah]

MCP Server Information

Server Name: OutageDeck (Remote)
Repository URL: https://github.com/outagedeck/mcp
Brief Description: First-party, keyless Streamable HTTP server for checking live status, incidents, and uptime across 172 cloud and SaaS vendors before debugging.

Basic Requirements

• Open Source: The first-party distribution metadata and documentation repository is MIT-licensed. The hosted vendor service falls under ToolHive's documented first-party proprietary-service exception.
• MCP Compliant: The public endpoint negotiates MCP 2025-06-18; initialize, notifications/initialized, and tools/list pass against the live Streamable HTTP endpoint.
• Active Development: The repository has current tagged releases through v1.1.2 and was updated on 2026-08-05.
• Documentation: The README documents client setup, all 14 tools, authentication boundaries, and the trust model.
• Security Contact: The repository contains SECURITY.md and a public security contact.

Submitter Checklist

• I have read the current Registry Inclusion Criteria and MCP Server Inclusion Criteria.
• This server meets the basic requirements listed above.
• I understand this will undergo automated and manual review.

Ready-to-review metadata

• Canonical Official MCP Registry record: com.outagedeck/outagedeck-status v1.1.0
• Remote endpoint: https://outagedeck.com/api/mcp
• Transport: streamable-http
• Authentication: none for the nine public read-only tools; five account-scoped tools require a user-supplied OutageDeck API key
• Suggested catalog name: outagedeck-remote
• Suggested tier: Official (this is the service vendor's first-party repository)
• Suggested tags: remote, monitoring, status, incidents, uptime, cloud, devops
• Icon: https://raw.githubusercontent.com/outagedeck/mcp/main/assets/logo.png
• Documentation: https://outagedeck.com/developers/mcp?utm_source=toolhive&utm_medium=registry&utm_campaign=toolhive_catalog

Public read-only tools: get_provider_status, check_my_stack, list_active_incidents, get_incident_details, get_uptime, get_outage_report, search_providers, search, and fetch.

Account-scoped tools: list_custom_providers, add_custom_provider, update_custom_provider, remove_custom_provider, and watch_provider.

The server reads vendors' official status feeds and reports source links and freshness. Public checks require no local execution, package, environment variable, or credential.

Maintainer affiliation: first-party OutageDeck submission. This issue was prepared and posted with AI assistance; all claims above were checked against the live endpoint and public repository.