MCP server list / devops-status-mcp-server
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 335.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 373 ms.
- Address
- https://devops-status.caseyjhand.com/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.cyanheads/
devops-status-mcp-server - Transport
- streamable HTTP
streamable-http - Host
devops-status.caseyjhand.com
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- devops-status-mcp-server
- Version:
- 0.8.0
- MCP features it lists:
- logging, resources, tools, prompts
- Tool names:
devops_list_vendorsdevops_status_checkdevops_get_incidentsdevops_watch_stackdevops_check_certsdevops_check_dnsdevops_suggest_action- Instructions excerpt:
- 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, …
Reported Aug 17, 2026, 05:01 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 133 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 465 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 298 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 373 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.