Devops Status Mcp Server
Give your coding agent live vendor status, certificate health, DNS checks, and structured incident steps without tab-hopping status pages during outages.
Overview
DevOps Status MCP is an Operate-phase MCP server that lets coding agents check vendor status pages, TLS certificates, DNS propagation, and incident playbooks in one protocol.
What is this MCP server?
- Aggregates public vendor status pages for dependency health during incidents
- TLS certificate inspection for expiry and chain issues on your domains
- DNS propagation checks to separate registrar, CDN, and caching problems
- Incident-response playbooks exposed as MCP tools for agent-guided triage
- SSRF-safe defaults with optional DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS for trusted intranet use
- Package version 0.2.2
- npm identifier @cyanheads/devops-status-mcp-server
- Remote MCP URL https://devops-status.caseyjhand.com/mcp (streamable-http)
Community signal: 1 GitHub stars.
What problem does it solve?
During an outage you waste minutes opening ten status tabs and guessing whether DNS, TLS, or a third party is at fault.
Who is it for?
Indie operators shipping web SaaS or APIs who want agent-driven triage when users report errors or deploys look green but traffic fails.
Skip if: Teams that need full APM, log aggregation, or synthetic monitoring inside one vendor console without any external HTTP checks.
What do I get? / Deliverables
Your agent can pull structured dependency and infra checks from chat and follow playbook steps without leaving the IDE.
- Agent-callable status, TLS, DNS, and playbook tool results during incidents
- Local stdio or remote HTTP MCP connection per server.schema.json remotes
Recommended MCP Servers
Journey fit
Production and launch-adjacent reliability work sits in Operate; this server is built for when something is already live and you need fast external dependency truth. Monitoring is the canonical shelf because the core tools poll status feeds, TLS expiry, and DNS propagation—the same signals you watch in an on-call or post-deploy smoke check.
How it compares
MCP integration for status and cert/DNS probes, not a replacement for Datadog, Sentry, or PagerDuty.
Common Questions / FAQ
Who is DevOps Status MCP for?
Solo builders and small devops-minded teams who want their AI coding agent to verify third-party outages, certs, and DNS during production incidents.
When should I use DevOps Status MCP?
Use it in Operate when symptoms could be upstream—after deploys, certificate renewals, DNS changes, or user reports of intermittent failures.
How do I add DevOps Status MCP to my agent?
Install @cyanheads/devops-status-mcp-server from npm with Bun, run the stdio start script in your MCP config, or point the client at the streamable-http remote URL from server.json.