Potencialize seu agente
A URL do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
https://devops-status.caseyjhand.com/mcpO botão do Claude acima abre o Claude com o nome e a URL preenchidos. Você ainda precisa confirmar lá.
claude mcp add --transport http io.github.cyanheads-devops-status-mcp-server https://devops-status.caseyjhand.com/mcpRun in a terminal.
{ "mcpServers": { "io.github.cyanheads-devops-status-mcp-server": { "command": "npx", "args": [ "-y", "mcp-remote", "https://devops-status.caseyjhand.com/mcp" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirPublic Hosted Server: https://devops-status.caseyjhand.com/mcp
Status pages for 53 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.
All resource data is also reachable via tools. Tool-only agents are fully supported.
devops_list_vendors toolquery (name and slug, case-insensitive) and optional category: cloud, cdn-edge, dev-platform, data, comms, auth, monitoring, ainotice naming what missedaws, gcp, azure, azure-devops, gitlab, neon, slack, and redis-cloud use native-API adapters. Statuspage-compatible pages not in the registry work by passing a raw base URL to other toolsBuilt-in vendor registry:
devops_status_check toolgithub, 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 nameserror field). Results are cached for 60 seconds (cached: true), and summary counts operational / degraded / down / maintenance / unavailablenextToolSuggestions pre-fills a devops_suggest_action call for each vendor with an active problemdevops_get_incidents toolfilter: all (default), active, resolved, or scheduled (maintenance windows only). limit (default 20, max 50) with offset for pagingsource: 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. match keeps incidents whose title or component names contain every word given (up to 200 characters)truncated: true and nextOffset. full_updates: true keeps every update on a single oversized incidentinvalid_since and invalid_until (filter: "active" or "scheduled", or until before since)resolved for Azure, scheduled for AWS, Azure, Azure DevOps, Google Cloud, and Slackdevops_watch_stack toolvendors (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 restartMCP_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_requiredhealth: all_operational / maintenance / degraded / partial_outage / major_outage / unknown (a vendor could not be reached). component_limit and nextToolSuggestions work as in devops_status_checkdevops_check_certs toolhost: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 resendwarning 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 portsstatus: "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 errortimeout_ms is one deadline per domain (max 15000)devops_check_dns toolhost:port; the first 10 domains are queried (up to 100 accepted) and the rest come back in deferred_domains. IP addresses get their own error rowpartial_resolution (some resolvers did not answer) is a real problem; value_variation (different values) is normal for anycast or geo-steered domainsresolvers take public IP literals, first 5 queried and the rest in deferred_resolvers; private and loopback addresses need DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS=true. timeout_ms applies per domain and resolver (max 10000)devops_suggest_action toolincident_summary, affected_components, and vendor_indicator add a subsystem section and severity-based urgencynextToolSuggestions pre-fills follow-up calls, including cert and DNS checks when your_domain is given. With DEVOPS_STATUS_DISABLE_ACTIVE_PROBES=true, guidance uses manual commands (dig, openssl s_client) insteaddevops-status://vendors/{name} resourcestatuspage, statusio, slack, aws, gcp, azure, azure-devops, firehydrant), and component_scope_prefix where a vendor covers part of a shared page (sendgrid)devops_list_vendorsBuilt on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.
DevOps-status-specific:
devops_watch_stack saves named vendor lists for repeat checks and pre-deploy sweepsdevops_suggest_action is deterministic, with no LLM sampling dependencyAgent-friendly output:
error fieldscached and checked_at on every status result show when data was fetchednone / minor / major / critical / maintenance) let callers branch on datanextToolSuggestions pre-fills follow-up tool arguments from incident contextA public instance is available at https://devops-status.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:
{
"mcpServers": {
"devops-status-mcp-server": {
"type": "streamable-http",
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}
No API key required. Add the following to your MCP client configuration file:
{
"mcpServers": {
"devops-status-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": ["@cyanheads/devops-status-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info"
}
}
}
}
Or with npx (no Bun required):
{
"mcpServers": {
"devops-status-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@cyanheads/devops-status-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info"
}
}
}
}
Or with Docker:
{
"mcpServers": {
"devops-status-mcp-server": {
"type": "stdio",
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "MCP_TRANSPORT_TYPE=stdio",
"ghcr.io/cyanheads/devops-status-mcp-server:latest"
]
}
}
}
For Streamable HTTP, set the transport and start the server:
MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
# Server listens at http://localhost:3010/mcp
git clone https://github.com/cyanheads/devops-status-mcp-server.git
cd devops-status-mcp-server
bun install
cp .env.example .env
# edit .env if you want to override defaults
No API keys required. All environment variables are optional.
An invalid DEVOPS_STATUS_* value stops startup with an error naming the variable.
See .env.example for the full list of optional overrides.
Build and run:
bun run rebuild
bun run start:stdio
# or
bun run start:http
Run checks and tests:
bun run devcheck # Lint, format, typecheck, security
bun run test # Vitest test suite
bun run lint:mcp # Validate MCP definitions against spec
docker build -t devops-status-mcp-server .
docker run --rm -p 3010:3010 devops-status-mcp-server
The 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.
See CLAUDE.md for development guidelines and architectural rules. The short version:
try/catch in tool logicctx.log for request-scoped logging, ctx.state for tenant-scoped storagesrc/mcp-server/*/definitions/index.tsdevops_check_certs and devops_check_dns use only Node.js stdlib — add no external deps for these pathsIssues are welcome. Run checks and tests before submitting:
bun run devcheck
bun run test
Apache-2.0 — see LICENSE for details.
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
{ "mcpServers": { "io.github.cyanheads-devops-status-mcp-server": { "url": "https://devops-status.caseyjhand.com/mcp", "headers": {} } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração http para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
O publicador lista estas variáveis de ambiente: MCP_LOG_LEVEL, DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS, DEVOPS_STATUS_DISABLE_ACTIVE_PROBES, MCP_TRANSPORT_TYPE, MCP_HTTP_HOST, MCP_HTTP_PORT, MCP_HTTP_ENDPOINT_PATH, MCP_AUTH_MODE.
Devops Status é acessado por HTTP.
Última verificação: 2026-11-09. Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.