# devops-status-mcp-server

The devops-status-mcp-server MCP server checks vendor outages, DNS responses and TLS certificates, and provides an incident playbook for active issues.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · 404 installs · ★ 3 repo stars
- Author: cyanheads
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/cyanheads/devops-status-mcp-server
- Updated: 2026-10-17
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/devops-status-mcp-server

## What it does

The server turns vendor status data into a consistent view of current health, affected components and incident history. Its built-in registry covers 53 services, including AWS, GitHub, Slack and Azure. For a vendor with an active issue, it can prepare an incident-response playbook and follow-up tool calls.

Separate tools inspect TLS certificates through a handshake and compare DNS answers from Google, Cloudflare and Quad9. DNS checks report resolver delays and differences between answers; neither DNS nor certificate checks relies on an external API. Connect the server over HTTP using the command below.

## Requirements
- Remote server: `https://devops-status-mcp-server--cyanheads.run.tools`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http devops-status-mcp-server https://devops-status-mcp-server--cyanheads.run.tools
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add devops-status-mcp-server --url https://devops-status-mcp-server--cyanheads.run.tools
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "devops-status-mcp-server": {
            "url": "https://devops-status-mcp-server--cyanheads.run.tools"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "devops-status-mcp-server": {
            "type": "http",
            "url": "https://devops-status-mcp-server--cyanheads.run.tools"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http devops-status-mcp-server https://devops-status-mcp-server--cyanheads.run.tools
```

## When to use it
- check which cloud or work services are having an outage
- retrieve a vendor’s incident timeline and affected components
- compare DNS answers from Google, Cloudflare and Quad9
- inspect a domain’s TLS certificate and expiry
- get response steps for a vendor incident

## Example prompts
- Check the current status of AWS, GitHub and Slack.
- Show recent incidents for `github` and list the affected components.
- Compare DNS answers for my domain across the resolvers and suggest steps for an AWS outage.

## Similar
- [render-domains](https://affpapa.org/en/nevibecode/skills/render-domains.md) — skill · 426 installs
- [investigating-incidents-with-aws-devops-agent](https://affpapa.org/en/nevibecode/skills/investigating-incidents-with-aws-devops-agent.md) — skill · 1600 installs
- [devops-troubleshooter](https://affpapa.org/en/nevibecode/agents/devops-troubleshooter.md) — subagent · 2328 installs
- [devops-incident-responder](https://affpapa.org/en/nevibecode/agents/devops-incident-responder.md) — subagent · 206 installs
- [devops-oncall](https://affpapa.org/en/nevibecode/plugins/devops-oncall.md) — plugin · ★ 41430 repo stars
- [infrastructure-compliance-auditor](https://affpapa.org/en/nevibecode/skills/infrastructure-compliance-auditor.md) — skill · 118 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
