devops-status-mcp-server
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
https://devops-status.caseyjhand.com/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- devops-status-mcp-server
- Version
- 0.8.0
- Capability keys
- logging, resources, tools, prompts
- Tool names
- devops_list_vendors, devops_status_check, devops_get_incidents, devops_watch_stack, devops_check_certs, devops_check_dns, devops_suggest_action
Infrastructure health and incident intelligence for DevOps agents. No API keys required — fully public data sources. Vendor registry: 51 verified vendors across cloud, CDN, dev-platform, data, comms, auth, monitoring, and AI categories — Atlassian Statuspage plus native adapters for AWS Health, Google Cloud Service Health, Status.io (GitLab, Neon), Slack, and Firehydrant (Redis Cloud), all normalized to one shape. Workflow: devops_list_vendors (discover slugs) → devops_status_check (health snapshot) → devops_get_incidents (incident history) → devops_suggest_action (response playbook). devops_watch_stack persists a named vendor list in session state for repeat health sweeps. devops_check_certs and devops_check_dns work for any domain — not just registered vendors.
Reported Aug 17, 2026, 05:01 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 133ms
- respondsMCP initialize · 8s limit · HTTP 200 · 465ms
- respondsMCP initialize · 8s limit · HTTP 200 · 298ms
- respondsMCP initialize · 8s limit · HTTP 200 · 373ms