# devops-status-mcp-server MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-cyanheads-devops-status-mcp-server
- Repository: https://github.com/cyanheads/devops-status-mcp-server

## Install
- Command: `npx -y @cyanheads/devops-status-mcp-server`
- Endpoint: https://devops-status.caseyjhand.com/mcp
- Auth: Not captured

## Setup notes
- Package: Npm @cyanheads/devops-status-mcp-server v0.2.0
- Environment variable: MCP_LOG_LEVEL (default info)
- Environment variable: DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS (default false)
- Package: Npm @cyanheads/devops-status-mcp-server v0.2.0
- Environment variable: MCP_HTTP_HOST (default 127.0.0.1)
- Environment variable: MCP_HTTP_PORT (default 3010)
- Environment variable: MCP_HTTP_ENDPOINT_PATH (default /mcp)
- Environment variable: MCP_AUTH_MODE (default none)
- Environment variable: MCP_LOG_LEVEL (default info)
- Environment variable: DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS (default false)
- Remote endpoint: https://devops-status.caseyjhand.com/mcp

## Tools
- devops_list_vendors (Devops List Vendors) - List vendors in the built-in registry, optionally filtered by category or name search. Returns slug, display name, category, and Statuspage base 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. Endpoint: https://devops-status.caseyjhand.com/mcp
- devops_status_check (Devops Status Check) - Check the current health status for one or more vendors. Accepts registered vendor slugs (e.g., "github", "cloudflare") or raw Statuspage base URLs. 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. Endpoint: https://devops-status.caseyjhand.com/mcp
- devops_get_incidents (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. Endpoint: https://devops-status.caseyjhand.com/mcp
- devops_watch_stack (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"). Endpoint: https://devops-status.caseyjhand.com/mcp
- devops_check_certs (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. Endpoint: https://devops-status.caseyjhand.com/mcp
- devops_check_dns (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). Endpoint: https://devops-status.caseyjhand.com/mcp
- devops_suggest_action (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. Endpoint: https://devops-status.caseyjhand.com/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.cyanheads
- Version: 0.2.0
- Runtime: Npm
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 31, 2026
- Source: https://registry.modelcontextprotocol.io