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

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

0 tools GitHub

No known CVEs

No license

Maintenance unknown

No commit data

Works with most clients

Transport:

0 tools

Token cost not measured

Edit this pageView history

DevOps

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-cyanheads-devops-status-mcp-server": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-cyanheads-devops-status-mcp-server)](https://mcppedia.org/s/io-github-cyanheads-devops-status-mcp-server)

Read me

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

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

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

0/100across 5 weighted dimensions

How we score →

0255075100

−100

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.cyanheads/devops-status-mcp-server safe to use?: io.github.cyanheads/devops-status-mcp-server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.cyanheads/devops-status-mcp-server?: io.github.cyanheads/devops-status-mcp-server can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.cyanheads/devops-status-mcp-server?: io.github.cyanheads/devops-status-mcp-server is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Similar servers

Others in devops

View all →

Mcp Gitlab94

MCP server for using the GitLab API

1.6k 12

Alibabacloud Devops Mcp Server92

Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.

116 7

Mcp Gitlab Server92

Enhanced MCP server for GitLab: group projects listing and activity tracking

51 2

Mcp Server Kubernetes92

MCP Server for kubernetes management commands

1.4k 22

MCP Security Weekly

Get CVE alerts and security updates for io.github.cyanheads/devops-status-mcp-server and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Tools

Seven tools in three capability groups — vendor status (Atlassian Statuspage, 26 built-in vendors + raw-URL passthrough), pure-TypeScript cert/DNS checks (any domain), and incident-response guidance:

Tool

Description

devops_list_vendors

List vendors in the built-in registry, optionally filtered by name or category. Returns slug, display name, category, and Statuspage base URL.

devops_status_check

Check the current health status for one or more vendors. Returns per-vendor indicator (none / minor / major / critical), 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 persisted in session state. Pass vendors once to save the list; subsequent calls reuse it. 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. 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

Frequently Asked Questions

Is io.github.cyanheads/devops-status-mcp-server safe to use?

io.github.cyanheads/devops-status-mcp-server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.cyanheads/devops-status-mcp-server?

io.github.cyanheads/devops-status-mcp-server can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with io.github.cyanheads/devops-status-mcp-server?

io.github.cyanheads/devops-status-mcp-server is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

@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

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 Statuspage base URL.
`devops_status_check`	Check the current health status for one or more vendors. Returns per-vendor indicator (`none` / `minor` / `major` / `critical`), 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 persisted in session state. Pass `vendors` once to save the list; subsequent calls reuse it. 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. 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

... View full README on GitHub