devops-status-mcp-server
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
- Devops List Vendors: List vendors in the built-in registry, optionally filtered by category or name search. Returns slug, display name, category, and status page URL for each entry. Use to discover th
- Devops Status Check: Check the current health status for one or more vendors. Accepts registered vendor slugs (e.g., "github", "aws", "gitlab") or raw Atlassian Statuspage base URLs. Registry entries
- Devops Get Incidents: Fetch incident history and scheduled maintenance windows for a vendor. Returns full incident timeline — each investigator update, affected components, and resolution. Filter by s
What data it sees
Do you need an account
No: the server works without sign-in
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
Server tool list (7)
Raw names from tools/list. Only developers need these.
| devops_list_vendors | List vendors in the built-in registry, optionally filtered by category or name search. Returns slug, display name, category, and status page URL for each entry. Use to discover the correct slug to pass to other tools, or to see which vendors are available before configuring a stack. |
| devops_status_check | Check the current health status for one or more vendors. Accepts registered vendor slugs (e.g., "github", "aws", "gitlab") or raw Atlassian Statuspage base URLs. Registry entries are served by each vendor's native status API (Statuspage, Status.io, Slack, AWS Health, Firehydrant) and normalized to one shape. Returns per-vendor operational indicator (none = all clear, minor, major, critical), degraded components, and active incidents. Use mode: "detailed" for full component lists and maintenance windows. Batch-friendly — pass a list to check your full stack in one call. |
| devops_get_incidents | Fetch incident history and scheduled maintenance windows for a vendor. Returns full incident timeline — each investigator update, affected components, and resolution. Filter by status to focus on active incidents (use before deploy), resolved history (for postmortem), or upcoming maintenance windows. |
| devops_watch_stack | Check the health of a named vendor stack — a saved list of vendors representing your infrastructure dependencies. On the first call, provide vendors to define the stack; subsequent calls can omit vendors to reuse the persisted list. Returns a unified health snapshot with an aggregate rollup plus per-vendor detail. Ideal for morning status checks or pre-deploy sweeps. Multiple stacks can coexist (e.g., "production", "staging"). |
| devops_check_certs | Inspect SSL/TLS certificate health for one or more domains by performing a real TLS handshake. Works for any internet-accessible domain — no vendor registry required. Reports days to expiry (flagged at < 30 days warning and < 7 days critical), certificate subject and SANs, issuer, chain depth, TLS protocol version negotiated (flags TLS 1.0/1.1 as insecure), cipher suite, and HSTS presence. |
| devops_check_dns | Resolve DNS records and verify propagation for one or more domains across multiple public resolvers. Works for any domain — no vendor registry required. Reports records found (A/AAAA/CNAME/MX/TXT/NS), resolution latency per resolver, and discrepancies between resolvers (propagation gaps). |
| devops_suggest_action | Return an incident-response playbook tailored to a vendor degradation, with pre-filled follow-up tool calls. Synthesizes category-specific guidance (cloud, CDN, dev-platform, auth, etc.) from built-in incident knowledge and the provided context. Use after devops_status_check or devops_get_incidents surfaces a problem to determine what to investigate next. |