Devops Status MCP Server

Name: Devops Status MCP Server
Author: cyanheads

by cyanheadsversion 0.11.1i★ –iComputer or cloud

Registry nameio.github.cyanheads/devops-status-mcp-server

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
Can do 7 things (tools) devops_list_vendors, devops_status_check, devops_get_incidents, devops_watch_stack …
You fill in yourself: MCP_LOG_LEVEL, DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS, DEVOPS_STATUS_DISABLE_ACTIVE_PROBES

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://devops-status.caseyjhand.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "devops-status": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/devops-status-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS": "your-value",
        "DEVOPS_STATUS_DISABLE_ACTIVE_PROBES": "your-value"
      }
    }
  }
}

Run this in your terminal

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

Or run it on your computer

claude mcp add devops-status --env MCP_LOG_LEVEL=your-value --env DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS=your-value --env DEVOPS_STATUS_DISABLE_ACTIVE_PROBES=your-value -- npx -y @cyanheads/devops-status-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "devops-status": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/devops-status-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS": "your-value",
        "DEVOPS_STATUS_DISABLE_ACTIVE_PROBES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "devops-status": {
      "type": "http",
      "url": "https://devops-status.caseyjhand.com/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "devops-status": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/devops-status-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS": "your-value",
        "DEVOPS_STATUS_DISABLE_ACTIVE_PROBES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://devops-status.caseyjhand.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

MCP_LOG_LEVEL env
Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').
DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS env
When 'true', disables the SSRF guards on user-supplied status-page URLs, devops_check_certs hosts, and devops_check_dns resolver IPs. For trusted local/intranet deployments only. Leave unset or 'fals…
DEVOPS_STATUS_DISABLE_ACTIVE_PROBES env
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-te…

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

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 sta
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, Googl
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 maintena
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 saved list. Stacks are saved per authenticated caller, or per l
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
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/CAA/SOA), resolution latency per resolver, and a typed outcome p
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 d

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account cyanheads, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 470 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
✓ Pass
No hidden instructions in tool descriptions
Read 7 tool descriptions and found no hidden instructions to the AI

Compared with others in Developer toolsi

More stars than 0% of the other 1394 servers in this category
Published to the registry more recently than 86% of the other 1394 servers in this category
Basic checks equal to or better than 100% of the other 1394 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Devops Status MCP Server safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.11.1) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@cyanheads/devops-status-mcp-server Check vendor status pages, inspect SSL/TLS certificates, verify DNS propagation, and get incident-response playbooks via MCP. STDIO or Streamable HTTP. 7 Tools • 1 Resource

Public Hosted Server: https://devops-status.caseyjhand.com/mcp

Overview

Status pages for 71 vendors — AWS, Google Cloud, Azure, Slack, and more — in one normalized format. Check who's down, pull incident timelines, watch your stack, and get an incident-response playbook. Plus TLS certificate and DNS checks for any domain. No API keys required.

Tools

Tool	Description
`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.
`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.
`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.
`devops_watch_stack`	Check the health of a named vendor stack. Where the server identifies the caller (stdio, or HTTP with `jwt`/`oauth` auth), pass `vendors` once to save the list and later calls reuse it; on HTTP with `MCP_AUTH_MODE=none` nothing is saved and `vendors` is required on every call. Returns an aggregate health rollup plus per-vendor detail.
`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 on HTTP ports. Pure TypeScript — no external API.
`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.
`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.

Resources

Resource	Description
`devops-status://vendors/{name}`	Full registry entry for a vendor by slug — status page URL, category, and API type.

All resource data is also reachable via tools. Tool-only agents are fully supported.

Capability reference

`devops_list_vendors` tool

Optional free-text query (name and slug, case-insensitive) and optional category: cloud, cdn-edge, dev-platform, data, comms, auth, monitoring, ai
Returns slug (what to pass to other tools), display name, category, and status page URL; an empty result carries a notice naming what missed
71 built-in entries, most on Atlassian Statuspage; aws, gcp, azure, azure-devops, gitlab, neon, slack, redis-cloud, and the nine Datadog site entries (datadog for US1, datadog-us3, datadog-us5, datadog-eu1, datadog-uk1, datadog-ap1, datadog-ap2, datadog-us1-fed, datadog-us2-fed) use native-API adapters. Statuspage-compatible pages not in the registry work by passing a raw base URL to other tools
These Atlassian products have their own entry (jira, confluence, bitbucket, jira-service-management, atlassian-compass, atlassian-developer, trello, opsgenie, atlassian-statuspage, atlassian-guard). atlassian reads the umbrella page, which publishes no components and only cross-product incidents; any tool serving it says so in notice and names those slugs

Built-in vendor registry:

Category	Vendors
`cloud`	digitalocean, linode, aws, gcp, azure
`cdn-edge`	cloudflare, akamai
`dev-platform`	gitlab, github, azure-devops, npm, vercel, netlify, render, fly-io, circleci, travis-ci, snyk, atlassian, jira, confluence, bitbucket, jira-service-management, atlassian-compass, atlassian-developer, trello, figma, launchdarkly
`data`	mongodb-atlas, planetscale, supabase, neon, redis-cloud, elastic, influxdb, upstash, cloudinary, segment
`comms`	slack, discord, twilio, sendgrid, mailgun, hubspot, brevo, courier, loops
`auth`	auth0, clerk, workos, atlassian-guard
`monitoring`	datadog, datadog-us3, datadog-us5, datadog-eu1, datadog-uk1, datadog-ap1, datadog-ap2, datadog-us1-fed, datadog-us2-fed, sentry, new-relic, grafana-cloud, honeycomb, opsgenie, atlassian-statuspage
`ai`	openai, anthropic, elevenlabs, pinecone, cohere

`devops_status_check` tool

Accepts vendor slugs (e.g., github, aws) or raw Atlassian Statuspage base URLs, mixed freely. Up to 20 are checked per call; the rest come back in deferred_vendors with a notice to resend them. More than 100 entries is rejected (invalid_arguments)
mode: "summary" (default) returns the indicator, degraded components, and active incidents; mode: "detailed" adds the full component list (component_limit, default 50, clamped to 500) and scheduled maintenance windows. component_filter matches component or group names
A list longer than component_limit pages: each capped vendor returns next_component_offset, which you pass back as component_offset (applied after component_filter). degraded_components and active_incidents are complete on every page
One failing vendor never blocks the rest (per-vendor error field). Results are cached for 60 seconds (cached: true), and summary counts operational / degraded / down / maintenance / unavailable
indicator is the vendor's own rating, and a Statuspage page can keep it at none while an incident it rated minor or worse is open. summary counts each vendor at the worse of the two; incidents rated none or maintenance and scheduled windows never count as an outage
nextToolSuggestions pre-fills a devops_suggest_action call for each vendor with an active problem — the vendors counted degraded or down

`devops_get_incidents` tool

filter: all (default), active, resolved, or scheduled (maintenance windows only). limit (default 20, max 50) with offset for paging
Returns per-update bodies as plain text in chronological order, affected component names, duration in minutes for resolved incidents, and a shortlink. Google Cloud and AWS incidents also carry affected_locations (region ID, name, and whether it is still affected; on AWS, the one region the event names, or global). Each incident carries source: api, or history for an archive record (title, impact, times, and final message only)
since and until (YYYY-MM-DD, UTC) bound the start date and work with filter: "all" or "resolved"; since also reads the Statuspage history archive back up to 24 months, past the API's newest-50 limit; a call that hits that limit without since is told to set it. match keeps incidents whose title, component names, or (on Google Cloud and AWS) location names and IDs contain every space-separated term given (up to 200 characters); a term joined by punctuation, such as eu-central-1, must find its words together and in order within one of them
Responses are capped at 64,000 bytes per surface; a cut page sets truncated: true and nextOffset. full_updates: true keeps every update on a single oversized incident
Errors: invalid_since and invalid_until (filter: "active" or "scheduled", or until before since)
Feeds with no data for a filter return empty: resolved for Azure, scheduled for AWS, Azure, Azure DevOps, Google Cloud, and Slack. History is short where a vendor reads no archive: AWS keeps resolved events for a few hours, and Status.io (gitlab, neon) lists current incidents only. On those feeds a since earlier than the oldest record returned, or an until without since, gets a notice naming the date the feed starts

`devops_watch_stack` tool

Pass vendors (up to 20) once to save the stack under stack_name (1-64 characters; several stacks can coexist, e.g. "production"); later calls can omit vendors. Over 20 is rejected with stack_too_large. Saving works on stdio and on HTTP with MCP_AUTH_MODE=jwt|oauth; with the default in-memory storage, saved stacks do not survive a restart
On HTTP with MCP_AUTH_MODE=none nothing is saved: a call with vendors runs the sweep and returns stack_persisted: false, and a call without vendors fails with vendors_required
Aggregate health: all_operational / maintenance / degraded / partial_outage / major_outage / unknown (a vendor could not be reached), rolled up from the same per-vendor rating as summary. component_limit and nextToolSuggestions work as in devops_status_check; there is no component_offset, so a capped vendor's next_component_offset continues in devops_status_check

`devops_check_certs` tool

Accepts hostnames, IP addresses, host:port, or URLs; a port on the entry overrides port (default 443). The first 10 entries are inspected (up to 100 accepted); the rest come back in deferred_domains to resend
Reports days to expiry (warning under 30 days, critical under 7), subject and SANs, issuer, chain depth, TLS version (1.0 and 1.1 flagged insecure), cipher suite, and HSTS on HTTP ports
status: "critical" separates a hostname mismatch (hostname_verification_error) from an untrusted chain (authorization_error). Per-domain failures come back inline as status: "error" with the reason in error
timeout_ms is one deadline per domain (max 15000)

`dev

Only the beginning is shown; read the rest in the repo

Devops Status MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Overview

Tools

Resources

Capability reference

devops_list_vendors tool

devops_status_check tool

devops_get_incidents tool

devops_watch_stack tool

devops_check_certs tool

`dev

`devops_list_vendors` tool

`devops_status_check` tool

`devops_get_incidents` tool

`devops_watch_stack` tool

`devops_check_certs` tool