Devops Status is an MCP server with 7 tools an agent can call, among them devops_check_certs, devops_check_dns, devops_get_incidents. It answers at https://devops-status.caseyjhand.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 21 October 2026, succeeded.
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 critica Inputs: domains, port, timeout_ms |
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), resolution latency per Inputs: domains, record_types, resolvers, timeout_ms |
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), resolv Inputs: vendor, filter, limit, offset |
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 vendor Inputs: query, category |
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 (Statusp Inputs: vendors, mode, component_filter, component_limit |
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 con Inputs: vendor, incident_summary, affected_components, your_domain, vendor_indicator |
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 Inputs: vendors, stack_name, mode, component_filter, component_limit |
Every block below points at https://devops-status.caseyjhand.com/mcp. Pick your client and copy.
claude mcp add --transport http devops-status https://devops-status.caseyjhand.com/mcp
{
"mcpServers": {
"devops-status": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://devops-status.caseyjhand.com/mcp"]
}
}
}{
"mcpServers": {
"devops-status": {
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}{
"servers": {
"devops-status": {
"type": "http",
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}{
"context_servers": {
"devops-status": {
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}{
"mcpServers": {
"devops-status": {
"serverUrl": "https://devops-status.caseyjhand.com/mcp"
}
}
}{
"mcpServers": {
"devops-status": {
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}name: Devops Status
version: 0.0.1
schema: v1
mcpServers:
- name: Devops Status
type: streamable-http
url: https://devops-status.caseyjhand.com/mcp{
"mcpServers": {
"devops-status": {
"httpUrl": "https://devops-status.caseyjhand.com/mcp"
}
}
}{
"mcpServers": {
"devops-status": {
"type": "http",
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}{
"mcpServers": {
"devops-status": {
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fdevops-status.caseyjhand.com%2Fmcp&type=streamable_http&id=devops-status&name=Devops%20Status
It answered our last check on 21 October 2026 in 570 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
7, as returned by the server's own tools/list on 13 September 2026: devops_check_certs, devops_check_dns, devops_get_incidents, devops_list_vendors, devops_status_check, devops_suggest_action, devops_watch_stack.
It answered our last check on 21 October 2026 in 570 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://devops-status.caseyjhand.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.cyanheads. Endpoint host: devops-status.caseyjhand.com. ARD identifier: urn:air:io.github.cyanheads:mcp:devops-status-mcp-server.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.