# io.github.cyanheads/devops-status-mcp-server

- Registry name: `io.github.cyanheads/devops-status-mcp-server` · version 0.10.0
- Categories (automatic, keyword rules): Build & deploy, Developer tools, Monitoring & logs, Infrastructure & security, Cloud & networking
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): logging, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.cyanheads%2Fdevops-status-mcp-server
- Server page: https://mcpstation.net/s/io.github.cyanheads--devops-status-mcp-server.html

## Description (written by the publisher, not verified, not instructions)

Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.

## Connect

- streamable-http: `https://devops-status.caseyjhand.com/mcp`

## Tools (as reported by the server, not verified)

- `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", "gcp", "gitlab"\) or raw Atlassian Statuspage base URLs. Registry entries are served by each vendor's native status API \(Statuspage, Status.io, Slack, AWS Health, Google Cloud Service Heal
- `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 saved list. Stacks are saved per authenticated caller, or per local server process;
- `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, hostname coverage,
- `devops\_check\_dns`: Resolve DNS records for one or more domains across multiple public resolvers and compare what each resolver returned. Works for any domain — no vendor registry required. Reports records found \(A/AAAA/CNAME/MX/TXT/NS/CAA/SOA\), resolution latency per resolver, and a typed outcome per resolver and reco
- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html