Check vendor status pages, inspect SSL/TLS certificates, verify DNS propagation, and get incident-response playbooks via MCP. STDIO or Streamable HTTP.\n
\n\n[](https://github.com/cyanheads/devops-status-mcp-server/releases/latest/download/devops-status-mcp-server.mcpb) [](https://cursor.com/en/install-mcp?name=devops-status-mcp-server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBjeWFuaGVhZHMvZGV2b3BzLXN0YXR1cy1tY3Atc2VydmVyIl19) [](https://vscode.dev/redirect?url=vscode:mcp/install?%7B%22name%22%3A%22devops-status-mcp-server%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40cyanheads%2Fdevops-status-mcp-server%22%5D%7D)\n\n[](https://www.npmjs.com/package/@cyanheads/mcp-ts-core)\n\n
\n\n---\n\n## Tools\n\nSeven tools in three capability groups — vendor status (51 built-in vendors across Atlassian Statuspage, Status.io, Slack, AWS Health, Google Cloud Service Health, and Firehydrant backends, normalized to one shape, + raw Statuspage URL passthrough), pure-TypeScript cert/DNS checks (any domain), and incident-response guidance:\n\n| Tool | Description |\n|:-----|:------------|\n| `devops_list_vendors` | List vendors in the built-in registry, optionally filtered by name or category. Returns slug, display name, category, and status page URL. |\n| `devops_status_check` | Check the current health status for one or more vendors. Returns per-vendor indicator (`none` / `minor` / `major` / `critical` / `maintenance`), degraded components, and active incident summaries. |\n| `devops_get_incidents` | Fetch incident history for a vendor — active, resolved, or scheduled maintenance. Returns the full incident timeline with per-update bodies and affected components. |\n| `devops_watch_stack` | Check the health of a named vendor stack persisted in session state. Pass `vendors` once to save the list; subsequent calls reuse it. Returns an aggregate health rollup plus per-vendor detail. |\n| `devops_check_certs` | Inspect SSL/TLS certificate health for one or more domains via a real TLS handshake. Reports expiry, chain depth, protocol version, cipher suite, and HSTS presence. Pure TypeScript — no external API. |\n| `devops_check_dns` | Resolve DNS records and verify propagation for one or more domains across Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9). Reports per-resolver latency and resolver discrepancies. Pure TypeScript — no external API. |\n| `devops_suggest_action` | Instruction tool — returns a tailored incident-response playbook and pre-filled follow-up tool calls given a vendor name and optional incident context. No external calls; fully deterministic. |\n\n### `devops_list_vendors`\n\nDiscover available vendors before running status checks or configuring a stack.\n\n- Accepts an optional free-text `query` (matches name and slug, case-insensitive) and an optional `category` filter\n- Eight categories: `cloud`, `cdn-edge`, `dev-platform`, `data`, `comms`, `auth`, `monitoring`, `ai`\n- Returns slug (what to pass to other tools), display name, category, and status page URL\n- 51 built-in entries — well-known public vendors with verified status endpoints (most on Atlassian Statuspage; `aws`, `gcp`, `gitlab`, `neon`, `slack`, and `redis-cloud` served through native-API adapters)\n\nBuilt-in vendor registry:\n\n| Category | Vendors |\n|:---------|:--------|\n| `cloud` | digitalocean, linode, aws, gcp |\n| `cdn-edge` | cloudflare, akamai |\n| `dev-platform` | gitlab, github, npm, vercel, netlify, render, fly-io, circleci, travis-ci, snyk, atlassian, figma, launchdarkly |\n| `data` | mongodb-atlas, planetscale, supabase, neon, redis-cloud, elastic, influxdb, upstash, cloudinary, segment |\n| `comms` | slack, discord, twilio, sendgrid, mailgun, hubspot, brevo, courier, loops |\n| `auth` | auth0, clerk, workos |\n| `monitoring` | datadog, sentry, new-relic, grafana-cloud, honeycomb |\n| `ai` | openai, anthropic, elevenlabs, pinecone, cohere |\n\nMost registry entries are Atlassian Statuspage endpoints; `aws` (AWS Health Dashboard), `gcp` (Google Cloud Service Health), `gitlab` / `neon` (Status.io), `slack` (Slack's own status API), and `redis-cloud` (Firehydrant) are served through adapters that normalize into the same shapes, so every tool works identically for them. Azure remains out of the registry: its status feed is RSS with no severity or lifecycle field, so the normalized shapes cannot be filled from it without inventing values. Statuspage-compatible pages not listed here can still be reached by passing a raw base URL.\n\n---\n\n### `devops_status_check`\n\nBatch health snapshot across one or more vendors in a single call.\n\n- Accepts registered vendor slugs (e.g., `\"github\"`, `\"aws\"`) or raw Atlassian Statuspage base URLs (e.g., `\"https://www.githubstatus.com\"`) — mix freely\n- `mode: \"summary\"` (default): indicator + degraded components + active incidents\n- `mode: \"detailed\"`: adds full component list and scheduled maintenance windows\n- `Promise.allSettled` fan-out — one failing vendor does not block the rest; errors surface inline\n- Results served from a 60-second in-memory cache; `cached: true` flag on each result\n\n---\n\n### `devops_get_incidents`\n\nFull incident timeline for a vendor with filter support.\n\n- `filter: \"all\"` (default): incidents plus scheduled maintenances\n- `filter: \"active\"`: only incidents with status `investigating` / `identified` / `monitoring`\n- `filter: \"resolved\"`: only fully resolved incidents\n- `filter: \"scheduled\"`: only scheduled maintenance windows\n- Returns per-update bodies in chronological order, affected component names, duration in minutes (resolved incidents), and a direct shortlink to the incident page\n- Configurable `limit` (1–50) with `offset` for paging through longer history; a truncated result discloses the total and names the next `offset` to fetch\n- AWS exposes only currently-open events (no history feed) — `filter: \"resolved\"` and `filter: \"scheduled\"` are always empty for `aws`\n\n---\n\n### `devops_watch_stack`\n\nNamed, persisted vendor stack for recurring health sweeps.\n\n- On the first call, provide `vendors` to define the stack — it is saved to tenant-scoped session state under `stack_name`\n- Subsequent calls can omit `vendors`; the saved list is reused automatically\n- Multiple stacks coexist via distinct `stack_name` values (e.g., `\"production\"`, `\"data-layer\"`) — letters, digits, hyphens, and underscores, optionally separated by single dots or slashes, 1-64 characters\n- Aggregate health output: `all_operational` / `degraded` / `partial_outage` / `major_outage` / `unknown` (a vendor could not be reached — errored vendors count as `unavailable` and never roll up as `all_operational`)\n- Note: stack state is in-memory; it does not persist across server restarts\n\n---\n\n### `devops_check_certs`\n\nDirect TLS handshake inspection — no external API required.\n\n- Accepts bare hostnames (no `https://` prefix) — up to 10 per call\n- Reports: days to expiry (flagged `warning` at < 30 days, `critical` at < 7), certificate subject and SANs, issuer common name, chain depth, negotiated TLS version (flags 1.0 and 1.1 as insecure), cipher suite\n- HSTS detection: sends a minimal HTTP/1.1 GET over the same TLS socket, reads the `Strict-Transport-Security` response header\n- Per-domain failures are reported inline (status: `\"error\"`) rather than throwing — useful partial results when checking multiple domains\n- Configurable port (default 443) and timeout per domain\n\n---\n\n### `devops_check_dns`\n\nMulti-resolver DNS propagation check — no external API required.\n\n- Queries Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9) in parallel per domain\n- Supported record types: A, AAAA, CNAME, MX, TXT, NS (defaults to A, AAAA, MX, TXT)\n- Reports per-resolver latency, propagation discrepancies (where resolvers disagree), and human-readable flags\n- Custom resolver list supported — pass any IP addresses to test internal DNS or resolver-specific behavior\n- Up to 10 domains per call; per-domain timeouts configurable\n\n---\n\n### `devops_suggest_action`\n\nDeterministic incident-response guidance, no external calls.\n\n- Returns a markdown playbook tailored to the vendor's category (CDN outage vs. CI/CD outage vs. auth provider outage vs. AI service outage)\n- Accepts a vendor slug or display name (`aws` or `Amazon Web Services`) — resolved to the canonical slug so the pre-filled follow-up arguments stay valid\n- `nextToolSuggestions` pre-populated with arguments from the provided context — execute in sequence to gather diagnostic data\n- Optional `your_domain` populates cert and DNS check arguments automatically\n- Optional `incident_summary` / `affected_components` prepend a targeted section to the playbook and add a component re-check when they identify a subsystem (e.g. GitHub `Actions` → CI/CD-prioritized steps; Cloudflare `DNS` → DNS/TTL guidance)\n- Optional `vendor_indicator` — pass the `indicator` from `devops_status_check` to lead the playbook with severity-tailored urgency guidance (`none` / `minor` / `major` / `critical` / `maintenance`)\n- Falls back to generic guidance for unrecognized vendors\n- When `DEVOPS_STATUS_DISABLE_ACTIVE_PROBES=true`, suggestions and playbook text replace the unregistered probe tools with equivalent manual commands (`dig`, `openssl s_client`)\n\n---\n\n## Resources and prompts\n\n| Type | Name | Description |\n|:-----|:-----|:------------|\n| Resource | `devops-status://vendors/{name}` | Full registry entry for a vendor by slug — status page URL, category, API type. |\n\nAll resource data is also reachable via tools. Tool-only agents are fully supported.\n\n---\n\n## Features\n\nBuilt on [`@cyanheads/mcp-ts-core`](https://www.npmjs.com/package/@cyanheads/mcp-ts-core):\n\n- Declarative tool and resource definitions — single file per primitive, framework handles registration and validation\n- Unified error handling — handlers throw, framework catches, classifies, and formats\n- Pluggable auth: `none`, `jwt`, `oauth`\n- Swappable storage backends: `in-memory`, `filesystem`, `Supabase`, `Cloudflare KV/R2/D1`\n- Structured logging with optional OpenTelemetry tracing\n- STDIO and Streamable HTTP transports\n\nDevOps-status-specific:\n\n- **No API keys required** — every status backend is a public API; TLS and DNS use Node.js stdlib (`node:tls`, `node:dns`)\n- 51-vendor built-in registry covering cloud, CDN, dev-platform, data, comms, auth, monitoring, and AI categories; adapter layer normalizes Status.io, Slack, AWS Health, Google Cloud Service Health, and Firehydrant backends into the Statuspage shapes; extendable via raw Statuspage URL passthrough\n- 60-second in-memory cache on status reads shared across all tenants — prevents thundering-herd on batch calls\n- `devops_watch_stack` persists named vendor lists in tenant-scoped state for repeat morning checks or pre-deploy sweeps\n- `devops_suggest_action` dispatches category-specific playbooks deterministically — no LLM sampling dependency, works in all clients\n\nAgent-friendly output:\n\n- Batch tools (`devops_status_check`, `devops_watch_stack`, `devops_check_certs`, `devops_check_dns`) use `Promise.allSettled` — one failing target never blocks the rest; errors surface as inline `error` fields\n- `cached: true` / `checked_at` on every status result — agents know when data was fetched\n- Discriminated indicator and status enums (`none` / `minor` / `major` / `critical` / `maintenance`; `operational` / `degraded_performance` / `partial_outage` / `major_outage` / `under_maintenance`) — callers branch on data, not string parsing\n- `nextToolSuggestions` in `devops_suggest_action` pre-fills tool arguments from incident context — agents can execute the playbook mechanically\n\n---\n\n## Getting started\n\n### Public Hosted Instance\n\nA public instance is available at `https://devops-status.caseyjhand.com/mcp` — no installation required. Point any MCP client at it via Streamable HTTP:\n\n```json\n{\n \"mcpServers\": {\n \"devops-status-mcp-server\": {\n \"type\": \"streamable-http\",\n \"url\": \"https://devops-status.caseyjhand.com/mcp\"\n }\n }\n}\n```\n\n### Self-Hosted / Local\n\nNo API key required. Add the following to your MCP client configuration file:\n\n```json\n{\n \"mcpServers\": {\n \"devops-status-mcp-server\": {\n \"type\": \"stdio\",\n \"command\": \"bunx\",\n \"args\": [\"@cyanheads/devops-status-mcp-server@latest\"],\n \"env\": {\n \"MCP_TRANSPORT_TYPE\": \"stdio\",\n \"MCP_LOG_LEVEL\": \"info\"\n }\n }\n }\n}\n```\n\nOr with npx (no Bun required):\n\n```json\n{\n \"mcpServers\": {\n \"devops-status-mcp-server\": {\n \"type\": \"stdio\",\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@cyanheads/devops-status-mcp-server@latest\"],\n \"env\": {\n \"MCP_TRANSPORT_TYPE\": \"stdio\",\n \"MCP_LOG_LEVEL\": \"info\"\n }\n }\n }\n}\n```\n\nOr with Docker:\n\n```json\n{\n \"mcpServers\": {\n \"devops-status-mcp-server\": {\n \"type\": \"stdio\",\n \"command\": \"docker\",\n \"args\": [\n \"run\", \"-i\", \"--rm\",\n \"-e\", \"MCP_TRANSPORT_TYPE=stdio\",\n \"ghcr.io/cyanheads/devops-status-mcp-server:latest\"\n ]\n }\n }\n}\n```\n\nFor Streamable HTTP, set the transport and start the server:\n\n```sh\nMCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http\n# Server listens at http://localhost:3010/mcp\n```\n\n### Prerequisites\n\n- [Bun v1.3.0](https://bun.sh/) or higher (or Node.js v24+).\n- No API keys or external accounts required.\n\n### Installation\n\n1. **Clone the repository:**\n\n```sh\ngit clone https://github.com/cyanheads/devops-status-mcp-server.git\n```\n\n2. **Navigate into the directory:**\n\n```sh\ncd devops-status-mcp-server\n```\n\n3. **Install dependencies:**\n\n```sh\nbun install\n```\n\n4. **Configure environment:**\n\n```sh\ncp .env.example .env\n# edit .env if you want to override defaults\n```\n\n---\n\n## Configuration\n\nNo API keys required. All environment variables are optional.\n\n| Variable | Description | Default |\n|:---------|:------------|:--------|\n| `DEVOPS_STATUS_CACHE_TTL_MS` | In-memory cache TTL for vendor status reads (all backends) in milliseconds. | `60000` |\n| `DEVOPS_STATUS_FETCH_TIMEOUT_MS` | Per-request timeout for vendor status API calls (all backends) in milliseconds. | `8000` |\n| `DEVOPS_STATUS_CERT_TIMEOUT_MS` | Default `timeout_ms` for `devops_check_certs` (per-domain TLS handshake, milliseconds). A caller-passed `timeout_ms` overrides it. | `5000` |\n| `DEVOPS_STATUS_DNS_TIMEOUT_MS` | Default `timeout_ms` for `devops_check_dns` (per domain+resolver query, milliseconds). A caller-passed `timeout_ms` overrides it. | `3000` |\n| `DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS` | When `true`, disables SSRF guards for user-supplied URLs and domains. For trusted local/intranet deployments only. | `false` |\n| `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. | `false` |\n| `MCP_TRANSPORT_TYPE` | Transport: `stdio` or `http`. | `stdio` |\n| `MCP_HTTP_PORT` | Port for HTTP server. | `3010` |\n| `MCP_SESSION_MODE` | HTTP session handling: `stateless`, `stateful`, or `auto`. This server holds no per-session state, and the published container sets `stateless`. | `auto` (resolves to `stateful`) |\n| `MCP_AUTH_MODE` | Auth mode: `none`, `jwt`, or `oauth`. | `none` |\n| `MCP_LOG_LEVEL` | Log level (RFC 5424). | `info` |\n| `LOGS_DIR` | Directory for log files (Node.js only). | `/logs` |\n| `OTEL_ENABLED` | Enable [OpenTelemetry instrumentation](https://github.com/cyanheads/mcp-ts-core/tree/main/docs/telemetry). | `false` |\n\nSee [`.env.example`](./.env.example) for the full list of optional overrides.\n\n---\n\n## Running the server\n\n### Local development\n\n- **Build and run:**\n\n ```sh\n bun run rebuild\n bun run start:stdio\n # or\n bun run start:http\n ```\n\n- **Run checks and tests:**\n\n ```sh\n bun run devcheck # Lint, format, typecheck, security\n bun run test # Vitest test suite\n bun run lint:mcp # Validate MCP definitions against spec\n ```\n\n### Docker\n\n```sh\ndocker build -t devops-status-mcp-server .\ndocker run --rm -p 3010:3010 devops-status-mcp-server\n```\n\nThe Dockerfile defaults to HTTP transport, stateless session mode, and logs to `/var/log/devops-status-mcp-server`. OpenTelemetry peer dependencies are installed by default — build with `--build-arg OTEL_ENABLED=false` to omit them.\n\n---\n\n## Project structure\n\n| Path | Purpose |\n|:-----|:--------|\n| `src/index.ts` | `createApp()` entry point — registers tools, resources, and inits services. |\n| `src/config/` | Server-specific environment variable parsing and validation with Zod. |\n| `src/mcp-server/tools/` | Tool definitions (`*.tool.ts`). |\n| `src/mcp-server/resources/` | Resource definitions (`*.resource.ts`). |\n| `src/services/cert/` | `node:tls` — TLS handshake, X.509 parsing, expiry and protocol flagging. |\n| `src/services/dns/` | `node:dns` — multi-resolver DNS fan-out, propagation discrepancy detection. |\n| `src/services/statuspage/` | Statuspage public API client with 60-second in-memory cache. |\n| `src/services/status-adapters/` | Native-API adapters (Status.io, Slack, AWS Health, Google Cloud Service Health, Firehydrant) + `api_type` dispatch, normalizing into the Statuspage shapes. |\n| `src/services/vendor-registry/` | In-memory vendor registry loaded from `src/data/vendor-registry.ts`. |\n| `src/data/` | Static vendor registry data file (`vendor-registry.ts`). |\n| `tests/` | Vitest tests mirroring `src/`. |\n\n---\n\n## Development guide\n\nSee [`CLAUDE.md`](./CLAUDE.md) for development guidelines and architectural rules. The short version:\n\n- Handlers throw, framework catches — no `try/catch` in tool logic\n- Use `ctx.log` for request-scoped logging, `ctx.state` for tenant-scoped storage\n- Register new tools and resources via the barrels in `src/mcp-server/*/definitions/index.ts`\n- `devops_check_certs` and `devops_check_dns` use only Node.js stdlib — add no external deps for these paths\n\n---\n\n## Contributing\n\nIssues and pull requests are welcome. Run checks and tests before submitting:\n\n```sh\nbun run devcheck\nbun run test\n```\n\n---\n\n## License\n\nApache-2.0 — see [LICENSE](LICENSE) for details.\n",
"bytes": 19841,
"sha": "65ca5056f692de95963cf8768fb6c24975c51bcf648253b0f685b8f74839a9d6",
"repo_slug": "cyanheads/devops-status-mcp-server",
"fonte": "repo",
"truncated": false,
"api": "https://agentalog.com/api/listings/mcp_io_github_cyanheads_devops_status_mcp_se_52dc4a84/readme"
}