Devops Status MCP Server

by cyanheads Your server? Claim it

answering

Devops Status MCP Server is answering right now. Last checked 4 min ago. 116 installs a week from npm. It exposes 7 tools. Last commit 25 Aug 2026.

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

Installs per day peak 183 · avg 23 · +49% w/w

a month agotoday

Uptime history 47 days of history · worst day 0%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

375 ms

Response time

average over 24h

116

Installs / week

npm and PyPI

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 August 2026. No other catalogue keeps this.

25 Aug 7 tools changed the parameters they ask for devops_check_certs, devops_check_dns, devops_get_incidents and 4 more

25 Aug a tool changed version

Nothing serious here today

Today is the operative word: we check Devops Status MCP Server every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add devops-status-mcp-server --transport http https://devops-status.caseyjhand.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "devops-status-mcp-server": {
      "url": "https://devops-status.caseyjhand.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.devops-status-mcp-server]
url = "https://devops-status.caseyjhand.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "devops-status-mcp-server": {
      "url": "https://devops-status.caseyjhand.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "devops-status-mcp-server": {
      "url": "https://devops-status.caseyjhand.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: MCP_HTTP_HOST (The hostname for the HTTP server.), MCP_HTTP_PORT (The port to run the HTTP server on.), MCP_HTTP_ENDPOINT_PATH (The endpoint path for the MCP server.), MCP_AUTH_MODE (Authentication mode to use: 'none', 'jwt', or 'oauth'.), MCP_LOG_LEVEL (Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').), DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS (When 'true', disables SSRF guards for user-supplied URLs and domains. For trusted local/intranet deployments only. Leave unset or 'false' for hosted/public deployments.), DEVOPS_STATUS_DISABLE_ACTIVE_PROBES (When 'true', omits the arbitrary-target probe tools (devops_check_dns, devops_check_certs) from the registered tool surface; the five vendor-registry/incident tools remain. For shared/public multi-tenant instances. Leave unset or 'false' to register both tools.). The author declared them in the registry entry; get the values from the project itself.

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

devops

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, chain-trust verification, TLS protocol version negotiated (flags TLS 1.0/1.1 as insecure), cipher suite, and HSTS presence. The handshake completes even for a certificate clients would reject, so a broken certificate is reported rather than hidden behind a connection error: a hostname mismatch surfaces in cert.hostname_verification_error and a chain-trust failure (self-signed, untrusted root) in cert.authorization_error, both status "critical". If a domain fails to connect at all, check devops_check_dns first — the name may not resolve.

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 resolver, and a typed outcome per resolver and record type so "the domain does not exist" (nxdomain), "the resolver could not answer" (servfail), and "no record of this type" (nodata) stay distinguishable. Resolver disagreements are reported without asserting a cause: partial_resolution (some resolvers answered, others returned nothing) points at a real propagation or resolver problem, while value_variation (every resolver answered with different values) is the normal steady state for anycast and geo-steered domains. Pair with devops_check_certs when a domain resolves but TLS to it is failing.

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. Page through long histories with limit + offset — a truncated result discloses the total and returns the value to page with in nextOffset. Some vendor feeds cap their own history: when upstreamCeiling is present the vendor API returned everything it will serve, and older incidents are reachable only on the vendor status page, not at a higher offset. An empty result explains itself in notice.

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 Health, Firehydrant) and normalized to one shape. Returns per-vendor operational indicator (none = all clear, minor, major, critical, maintenance = scheduled window), degraded components, and active incidents. Use mode: "detailed" for component lists and maintenance windows, narrowed with component_filter and bounded by component_limit. Batch-friendly — pass a list to check your full stack in one call; a vendor that cannot be resolved or reached is reported in its own result row, so one bad entry never discards the rest.

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.

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. A vendor that cannot be resolved or reached is reported in its own row and left out of the saved stack, so one bad entry never discards the sweep. Ideal for morning status checks or pre-deploy sweeps. Multiple stacks can coexist (e.g., "production", "staging").

Endpoints

URL	Transport	State	Latency	Checked
https://devops-status.caseyjhand.com/mcp	streamable-http	answering	414 ms	4 min ago

Alternatives to Devops Status MCP Server

same job, measured the same way

Create Starter

by starter-series

Scaffold Starter Series projects and check release, deployment, security, and agent instructions.

256 installs/wk local only

AWS CLI MCP Server

by musaddiq-dev

Python MCP server for AWS CLI inspection and operations

71 installs/wk local only

MCP Health Monitor

by oaslananka

Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status

local only

Dingdawg Devops Agent

by dingdawg

DevOps AI. Deploy checks, incident analysis, infra audit. Learns from past failures.

49 installs/wk local only

The Deployer

by thedploy

Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.

310 installs/wk 6 tools answering

DeployIt Product Expert

by deployit

AI product expert answering from live source code, with sources and a verification status.

3 tools answering

RationalBloks

by rationalbloks

Deploy production REST APIs from JSON schemas in seconds. Manage projects, schemas, and deployments.

215 installs/wk 49 tools answering

Homebutler

by higangssh

Tells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox.

1 332 installs/wk local only

Devops Status MCP Server — questions

Answers built from our own checks of this server.

What can Devops Status MCP Server do?

It exposes 7 tools, read directly from the server on our last check. Among them: devops_check_certs, devops_check_dns, devops_get_incidents, devops_list_vendors, devops_status_check, devops_suggest_action and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Devops Status MCP Server working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 375 ms. The bar chart above shows every period we have measured.

How do I connect Devops Status MCP Server?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Devops Status MCP Server need an API key?

No. Devops Status MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Devops Status MCP Server?

It answers our handshake in 375 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Devops Status MCP Server?

The npm package @cyanheads/devops-status-mcp-server was installed 116 times in the last week. Week over week that is +49%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Devops Status MCP Server open source?

Yes — it is published under the Apache-2.0 licence, written in TypeScript, 2 stars on GitHub and 3 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.