Connect-MCP

io.github.cyanheads/devops-status-mcp-server

io.github.cyanheads/devops-status-mcp-server · v0.10.0

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

MCPremotelocal · npmno credentialsCloud & DevOps

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 7 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 100/100

What it does: 7 tools · 6 read, 1 write · Cloud & DevOps

Test call devops_list_vendors: worked (1,119 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://devops-status.caseyjhand.com/mcp
Package
registry:   npm
identifier: @cyanheads/devops-status-mcp-server
version:    0.10.0
transport:  stdio

Tools

7 tools listed at last check
  • 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 Heal
  • 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
  • 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 local server process;
  • 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,
  • 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 per resolver and reco
  • 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

Badge

Connect-MCP badge for io.github.cyanheads/devops-status-mcp-server

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.cyanheads/devops-status-mcp-server.svg)](https://clawy.uk/mcp/s/io.github.cyanheads/devops-status-mcp-server)

Repository