_ registry / mcp http-sse

devops-status-mcp-server

https://devops-status.caseyjhand.com

Registry code: 4005b115c348be4d

Infrastructure health and incident intelligence for DevOps agents. No API keys required — fully public data sources. Vendor registry: 51 verified vendors across cloud, CDN, dev-platform, data, comms, auth, monitoring, and AI categories — Atlassian Statuspage plus native adapters for AWS Health, Google Cloud Service Health, Status.io (GitLab, Neon), Slack, and Firehydrant (Redis Cloud), all normalized to one shape. Workflow: devops_list_vendors (discover slugs) → devops_status_check (health snapshot) → devops_get_incidents (incident history) → devops_suggest_action (response playbook).…

endpoint: https://devops-status.caseyjhand.com/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing
karma: 0 · newcomer

reachable

unknown

uptime

—

latency

—

last good check

priced tools

of 7 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts

distinct, expensive to fake

calls served

successful, last 30 days

_ what it can do 7 tools

7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

devops_list_vendors unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text search against vendor name and slug. Case-insensitive. E.g., \"cloud\", \"auth\", \"slack\"."
    },
    "category": {
      "enum": [
        "cloud",
        "cdn-edge",
        "dev-platform",
        "data",
        "comms",
        "auth",
        "monitoring",
        "ai"
      ],
      "type": "string",
      "description": "Filter to one category: cloud, cdn-edge, dev-platform, data, comms, auth, monitoring, or ai."
    }
  },
  "additionalProperties": false
}

arguments 25 lines

devops_status_check unknown never probed

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 Health, Firehydrant) and normalized to one shape. Returns per-vendor operational indicator (none = all clear, minor, major, critical, maintenance = scheduled window), degraded components, and active incidents. Use mode: "detailed" for component lists and maintenance windows, narrowed with component_filter and bounded by component_limit. Batch-friendly — pass a list to check your full stack in one call; a vendor that cannot be resolved or reached is reported in its own result row, so one bad entry never discards the rest.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "vendors"
  ],
  "properties": {
    "mode": {
      "enum": [
        "summary",
        "detailed"
      ],
      "type": "string",
      "default": "summary",
      "description": "summary: indicator + degraded components + active incidents only. detailed: adds the component list and scheduled maintenance windows."
    },
    "vendors": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "description": "A vendor slug (e.g., \"github\") or raw Atlassian Statuspage base URL."
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "Vendor slugs from the built-in registry (e.g., \"github\", \"aws\") or raw Atlassian Statuspage base URLs (non-Statuspage backends are supported via registry slugs only). Mix freely. Use devops_list_vendors to discover available slugs."
    },
    "component_limit": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 1,
      "description": "Maximum components returned per vendor in detailed mode (1-500). Large status pages publish hundreds of components, so a multi-vendor batch at a high limit returns a very large response; narrow with component_filter instead where possible."
    },
    "component_filter": {
      "type": "string",
      "description": "Case-insensitive substring matched against component names in detailed mode (e.g., \"api\" to check just the API components). Applied before component_limit, so it is the way to reach a component that the cap would otherwise omit. Ignored in summary mode."
    }
  },
  "additionalProperties": false
}

arguments 41 lines

devops_get_incidents unknown never probed

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. Page through long histories with limit + offset — a truncated result discloses the total and returns the value to page with in nextOffset. Some vendor feeds cap their own history: when upstreamCeiling is present the vendor API returned everything it will serve, and older incidents are reachable only on the vendor status page, not at a higher offset. An empty result explains itself in notice.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "vendor"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum incidents to return per call (1–50). Page through longer history with offset rather than raising this."
    },
    "filter": {
      "enum": [
        "all",
        "active",
        "resolved",
        "scheduled"
      ],
      "type": "string",
      "default": "all",
      "description": "all: incidents plus scheduled maintenances. active: only incidents with status investigating/identified/monitoring. resolved: only fully resolved incidents. scheduled: only scheduled maintenance windows. Not every vendor backend serves every filter — \"aws\" publishes currently-open events only (never resolved, no maintenance windows), and \"gcp\" and \"slack\" publish no maintenance windows. An empty result names which case applied."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Number of matching incidents to skip before applying limit, for paging through history. 0 (default) returns the most recent page; a truncated result returns the value to use next in the nextOffset field. Raising offset past the number of matches returns an empty list and says so."
    },
    "vendor": {
      "type": "string",
      "minLength": 1,
      "description": "Vendor slug (e.g., \"github\", \"aws\") or raw Atlassian Statuspage base URL. Use devops_list_vendors to find slugs."
    }
  },
  "additionalProperties": false
}

arguments 40 lines

devops_watch_stack unknown never probed

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 persisted list. Returns a unified health snapshot with an aggregate rollup plus per-vendor detail. A vendor that cannot be resolved or reached is reported in its own row and left out of the saved stack, so one bad entry never discards the sweep. Ideal for morning status checks or pre-deploy sweeps. Multiple stacks can coexist (e.g., "production", "staging").

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "mode": {
      "enum": [
        "summary",
        "detailed"
      ],
      "type": "string",
      "default": "summary",
      "description": "summary: indicator + degraded components + active incidents. detailed: adds component lists and maintenance windows."
    },
    "vendors": {
      "type": "array",
      "items": {
        "type": "string",
        "description": "A vendor slug (e.g., \"github\") or raw Atlassian Statuspage base URL."
      },
      "description": "Vendor slugs (e.g., \"github\", \"aws\") or raw Atlassian Statuspage base URLs. When provided, saves this list as the stack. When omitted, uses the previously saved list for stack_name."
    },
    "stack_name": {
      "type": "string",
      "default": "default",
      "pattern": "^[a-zA-Z0-9_-]+([./][a-zA-Z0-9_-]+)*$",
      "maxLength": 64,
      "minLength": 1,
      "description": "Name for this vendor stack. Defaults to \"default\". Use distinct names to manage multiple stacks (e.g., \"production\", \"data-layer\"). Letters, digits, hyphens, and underscores, optionally separated by single dots or slashes (\"prod.eu\", \"team/prod\"); 1-64 characters. No spaces or colons."
    },
    "component_limit": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 1,
      "description": "Maximum components returned per vendor in detailed mode (1-500). Large status pages publish hundreds of components, so a full stack at a high limit returns a very large response; narrow with component_filter instead where possible."
    },
    "component_filter": {
      "type": "string",
      "description": "Case-insensitive substring matched against component names in detailed mode (e.g., \"api\" to check just the API components). Applied before component_limit, so it is the way to reach a component that the cap would otherwise omit. Ignored in summary mode."
    }
  },
  "additionalProperties": false
}

arguments 43 lines

devops_check_certs unknown never probed

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, chain-trust verification, TLS protocol version negotiated (flags TLS 1.0/1.1 as insecure), cipher suite, and HSTS presence. The handshake completes even for a certificate clients would reject, so a broken certificate is reported rather than hidden behind a connection error: a hostname mismatch surfaces in cert.hostname_verification_error and a chain-trust failure (self-signed, untrusted root) in cert.authorization_error, both status "critical". If a domain fails to connect at all, check devops_check_dns first — the name may not resolve.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domains"
  ],
  "properties": {
    "port": {
      "type": "integer",
      "default": 443,
      "maximum": 65535,
      "minimum": 1,
      "description": "TLS port. Defaults to 443. Use 8443 or custom ports for non-standard HTTPS endpoints."
    },
    "domains": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "description": "Domain name without protocol (e.g., \"api.github.com\", \"example.com\")."
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "Domains to inspect. Do not include \"https://\" — pass the bare hostname. Up to 10 per call."
    },
    "timeout_ms": {
      "type": "integer",
      "default": 5000,
      "maximum": 15000,
      "minimum": 1000,
      "description": "Connection timeout per domain in milliseconds. Defaults to the DEVOPS_STATUS_CERT_TIMEOUT_MS env var (5000 when unset). Increase for slow or geographically distant endpoints."
    }
  },
  "additionalProperties": false
}

arguments 35 lines

devops_check_dns unknown never probed

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), resolution latency per resolver, and a typed outcome per resolver and record type so "the domain does not exist" (nxdomain), "the resolver could not answer" (servfail), and "no record of this type" (nodata) stay distinguishable. Resolver disagreements are reported without asserting a cause: partial_resolution (some resolvers answered, others returned nothing) points at a real propagation or resolver problem, while value_variation (every resolver answered with different values) is the normal steady state for anycast and geo-steered domains. Pair with devops_check_certs when a domain resolves but TLS to it is failing.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domains"
  ],
  "properties": {
    "domains": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "description": "A domain name to query (e.g., \"github.com\", \"api.example.com\")."
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "Domain names to query. Up to 10 per call."
    },
    "resolvers": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "description": "A resolver IP literal — IPv4 (\"8.8.8.8\"), IPv6 (\"2001:4860:4860::8888\"), or either with a port (\"1.1.1.1:53\", \"[2001:4860:4860::8888]:53\"). A hostname is rejected."
      },
      "default": [
        "8.8.8.8",
        "1.1.1.1",
        "9.9.9.9"
      ],
      "description": "Resolver IP addresses to query. Defaults to Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9). Add custom resolvers to test resolver-specific behavior. Each must be an IP literal, not a hostname; resolvers in private, loopback, or cloud-metadata ranges are rejected unless DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS=true."
    },
    "timeout_ms": {
      "type": "integer",
      "default": 3000,
      "maximum": 10000,
      "minimum": 1000,
      "description": "Query timeout per domain+resolver combination in milliseconds. Defaults to the DEVOPS_STATUS_DNS_TIMEOUT_MS env var (3000 when unset)."
    },
    "record_types": {
      "type": "array",
      "items": {
        "enum": [
          "A",
          "AAAA",
          "CNAME",
          "MX",
          "TXT",
          "NS"
        ],
        "type": "string"
      },
      "default": [
        "A",
        "AAAA",
        "MX",
        "TXT"
      ],
      "description": "DNS record types to resolve. Defaults to A, AAAA, MX, and TXT. Add NS to check nameserver delegation. Add CNAME when investigating redirect chains."
    }
  },
  "additionalProperties": false
}

arguments 63 lines

devops_suggest_action unknown never probed

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 surfaces a problem to determine what to investigate next.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "vendor"
  ],
  "properties": {
    "vendor": {
      "type": "string",
      "minLength": 1,
      "description": "Vendor slug or display name (e.g., \"cloudflare\", \"github\"). Used to tailor category-specific guidance (CDN outage vs. CI/CD outage vs. auth provider outage)."
    },
    "your_domain": {
      "type": "string",
      "description": "Your own domain or service URL. When provided, nextToolSuggestions will be pre-filled with your domain for cert and DNS checks."
    },
    "incident_summary": {
      "type": "string",
      "description": "Latest incident description or update body from devops_get_incidents. Paste the most recent update to get more targeted advice."
    },
    "vendor_indicator": {
      "enum": [
        "none",
        "minor",
        "major",
        "critical",
        "maintenance"
      ],
      "type": "string",
      "description": "Overall vendor status indicator from a prior devops_status_check call (its indicator field). When provided, the playbook leads with severity-tailored urgency guidance. Omit if status has not been checked yet."
    },
    "affected_components": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Component names affected (from devops_status_check degraded_components or devops_get_incidents affected_components). Used to tailor suggestions to the impacted subsystem."
    }
  },
  "additionalProperties": false
}

arguments 41 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/4005b115c348be4d/badge.svg)](https://brick.blue/agent/4005b115c348be4d)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on caseyjhand.com 70 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

usaspending.caseyjhand.com usaspending-mcp-server mcp · 18 tools
openfda.caseyjhand.com openfda-mcp-server mcp · 14 tools
open-meteo.caseyjhand.com open-meteo-mcp-server mcp · 11 tools
pubmed.caseyjhand.com pubmed-mcp-server mcp · 11 tools
openlibrary.caseyjhand.com openlibrary-mcp-server mcp · 10 tools
pubchem.caseyjhand.com pubchem-mcp-server mcp · 10 tools
reference-data.caseyjhand.com reference-data-mcp-server mcp · 10 tools
orcid.caseyjhand.com orcid-mcp-server mcp · 9 tools

62 more sit on this domain. All of them.