devops-status-mcp-server
An MCP server that provides tools to monitor vendor health status pages, inspect SSL/TLS certificates, verify DNS propagation, and access incident-response playbooks. It supports STDIO and Streamable HTTP transports and includes a built-in registry for major cloud and SaaS vendors.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
MCP endpoint (Streamable HTTP)
https://devops-status.caseyjhand.com/mcpWhat its tools do
7 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Read-only (6)
Can change data (1)
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Check current health status for multiple vendors like AWS, Azure, and Slack
- Inspect SSL/TLS certificate health and expiry for specific domains
- Resolve DNS records and verify propagation across multiple resolvers
- Fetch incident history and timelines for specific vendors
Source and maintenance
Community listingRegistry 0.11.1
- Maintenance checked
Protocol and capabilities
- Server
- devops-status-mcp-server 0.11.1
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 7 advertised
- Resources
- 1 advertised
- Resource templates
- 2 advertised
- Prompts
- 0 advertised
Server-advertised capabilities
{
"tools": {
"listChanged": true
},
"logging": {},
"prompts": {
"listChanged": true
},
"resources": {
"subscribe": true,
"listChanged": true
},
"extensions": {
"io.modelcontextprotocol/skills": {
"directoryRead": true
}
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
7 advertised
devops_list_vendors — Devops List Vendors
Advertised read-only
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_list_vendors input schema
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"query": {
"type": "string",
"description": "Substring search against vendor slug and display name. Case-insensitive; surrounding whitespace is ignored. 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
}devops_list_vendors output schema
{
"type": "object",
"anyOf": [
{
"not": {
"required": [
"error"
]
},
"required": [
"vendors",
"total",
"categories"
]
},
{
"required": [
"error"
]
}
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "JSON-RPC error code for this failure."
},
"data": {
"type": "object",
"properties": {
"reason": {
"type": "string",
"description": "Machine-readable failure mode."
},
"recovery": {
"type": "object",
"required": [
"hint"
],
"properties": {
"hint": {
"type": "string"
}
},
"description": "Actionable next step for the caller.",
"additionalProperties": {}
},
"retryable": {
"type": "boolean",
"description": "Whether retrying may succeed."
}
},
"additionalProperties": {}
},
"message": {
"type": "string",
"description": "Human-readable description of what went wrong."
}
},
"description": "Present when the call failed. Absent on success.",
"additionalProperties": {}
},
"total": {
"type": "number",
"description": "Total number of vendors returned."
},
"notice": {
"type": "string",
"description": "Why nothing matched and what to call next. Present only when vendors is empty."
},
"vendors": {
"type": "array",
"items": {
"type": "object",
"required": [
"slug",
"name",
"category",
"statuspage_url"
],
"properties": {
"name": {
"type": "string",
"description": "Display name of the vendor."
},
"slug": {
"type": "string",
"description": "Use this as the vendor identifier in other tools."
},
"category": {
"type": "string",
"description": "Vendor category (e.g., \"dev-platform\", \"ai\")."
},
"statuspage_url": {
"type": "string",
"description": "Status page base URL — the Statuspage API base for Statuspage-backed vendors, the public status page URL for adapter-backed vendors (aws, gcp, azure, azure-devops, gitlab, slack, neon, redis-cloud, and datadog with its datadog-* site entries)."
}
},
"description": "A vendor entry from the built-in registry.",
"additionalProperties": false
},
"description": "Matching vendors from the built-in registry."
},
"categories": {
"type": "array",
"items": {
"type": "string"
},
"description": "All available category values for use in the category filter."
}
},
"additionalProperties": false
}devops_list_vendors annotations
{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true
}devops_status_check — Devops Status Check
Advertised read-onlyOpen-world
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, Azure status, Azure DevOps status, Firehydrant, Datadog) and normalized to one shape. Returns per-vendor operational indicator as the vendor published it (none = no degradation reported, minor, major, critical, maintenance = scheduled window), degraded components, and active incidents; summary counts each vendor at the worse of its indicator and its worst open incident rated minor or worse. Use mode: "detailed" for component lists and maintenance windows, narrowed with component_filter, bounded by component_limit, and paged with component_offset. Batch-friendly — pass a list to check your full stack in one call; up to 20 vendors are checked per call, and any past the 20th come back in deferred_vendors to resend. A vendor that cannot be resolved or reached is reported in its own result row, so one bad entry never discards the rest. Every vendor with an active problem gets a pre-filled devops_suggest_action call in nextToolSuggestions.
devops_status_check input schema
{
"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": 100,
"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. The first 20 are checked, in the order given; entries past the 20th are returned unchecked in deferred_vendors to resend in another call. Lists longer than 100 are rejected."
},
"component_limit": {
"type": "integer",
"default": 50,
"maximum": 9007199254740991,
"minimum": 1,
"description": "Maximum components returned per vendor in detailed mode, at least 1. A value above 500 is reduced to 500, and notice says so; a longer list continues with component_offset. 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 and their group names in detailed mode (e.g., \"api\" to check just the API components, or a product or region a page groups components under). Applied before component_offset and component_limit, so it reaches a specific component without paging, and an offset pages within the filtered list. A filter that matches nothing for a vendor is reported in notice. Ignored in summary mode."
},
"component_offset": {
"type": "integer",
"default": 0,
"maximum": 9007199254740991,
"minimum": 0,
"description": "Components to skip per vendor, after component_filter and before component_limit. Pass a vendor's next_component_offset to continue its list. An offset past a vendor's last component returns an empty list for it, and notice says so. Ignored in summary mode."
}
},
"additionalProperties": false
}devops_status_check output schema
{
"type": "object",
"anyOf": [
{
"not": {
"required": [
"error"
]
},
"required": [
"results",
"deferred_vendors",
"summary",
"nextToolSuggestions"
]
},
{
"required": [
"error"
]
}
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"cap": {
"type": "number",
"description": "The per-vendor component_limit that was applied. Present only when truncated."
},
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "JSON-RPC error code for this failure."
},
"data": {
"type": "object",
"properties": {
"reason": {
"type": "string",
"examples": [
"vendor_not_found",
"target_blocked"
],
"description": "Machine-readable failure mode. Declared by this tool: `vendor_not_found`: No requested vendor among the first 20 could be checked and the first failure was a slug that matches no registry entry and is not a valid URL. `target_blocked`: No requested vendor among the first 20 could be checked and the first failure was a raw URL resolving to a private, loopback, or cloud-metadata address. Other values are possible when a failure originates below the handler."
},
"recovery": {
"type": "object",
"required": [
"hint"
],
"properties": {
"hint": {
"type": "string"
}
},
"description": "Actionable next step for the caller.",
"additionalProperties": {}
},
"retryable": {
"type": "boolean",
"description": "Whether retrying may succeed."
}
},
"additionalProperties": {}
},
"message": {
"type": "string",
"description": "Human-readable description of what went wrong."
}
},
"description": "Present when the call failed. Absent on success.",
"additionalProperties": {}
},
"shown": {
"type": "number",
"description": "Components returned across all vendors. Present only when truncated."
},
"notice": {
"type": "string",
"description": "Plain-language explanation of what this call left out or adjusted, in this order: vendors past the first 20 (listed in deferred_vendors); a component_limit above 500 reduced to 500; in detailed mode, how many components lie past the returned page and how to reach them (this tool again with that vendor and its next_component_offset as component_offset, component_filter to target one, or component_limit to raise a cap below 500), which vendors component_offset ran past the end of, and which checked vendors component_filter matched no component of, with how many each publishes; and last, for a vendor whose entry reads an umbrella status page with no components (atlassian), the slugs of the entries reading its product pages. Present only when one of these applies."
},
"results": {
"type": "array",
"items": {
"type": "object",
"required": [
"vendor",
"name",
"indicator",
"description",
"degraded_components",
"active_incidents",
"cached",
"checked_at",
"statuspage_url"
],
"properties": {
"name": {
"type": "string",
"description": "Display name of the vendor."
},
"error": {
"type": "string",
"description": "Why this vendor could not be checked — unreachable status API, timeout, non-2xx, or a response that is not a Statuspage payload. Reported here rather than thrown so one bad vendor does not fail the batch. Absent when the vendor was fetched successfully."
},
"cached": {
"type": "boolean",
"description": "True when this result was served from the in-memory status cache, shared across callers (60 s TTL by default), so its data can be up to that TTL older than checked_at."
},
"vendor": {
"type": "string",
"description": "Vendor slug or URL as provided."
},
"indicator": {
"enum": [
"none",
"minor",
"major",
"critical",
"maintenance"
],
"type": "string",
"description": "Overall health indicator, as the vendor published it: none = no degradation reported, minor = some degradation, major = significant outage, critical = complete outage, maintenance = scheduled window in progress, planned rather than a fault. A page can rate it from component statuses alone, so it can read none or maintenance while active_incidents lists an open incident rated minor or worse; summary, and devops_watch_stack's health, rate the vendor by the worse of the two."
},
"checked_at": {
"type": "string",
"description": "ISO 8601 UTC timestamp of this check — when this result was built, not when the status data was fetched; see cached."
},
"description": {
"type": "string",
"description": "Human-readable status description (e.g., \"All Systems Operational\")."
},
"all_components": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"group",
"status",
"description"
],
"properties": {
"name": {
"type": "string",
"description": "Component name as the status page publishes it — the leaf alone, without its group. Several leaves can share a name (one per region or product); group tells them apart."
},
"group": {
"type": [
"string",
"null"
],
"description": "Name of the group the status page files this component under — typically the product or region it belongs to — or null when it is not in a group."
},
"status": {
"type": "string",
"description": "Component operational status."
},
"description": {
"type": [
"string",
"null"
],
"description": "Component description, or null if not provided."
}
},
"description": "A component entry.",
"additionalProperties": false
},
"description": "Components including operational ones, narrowed by component_filter (matched against name and group) when given, starting at component_offset (devops_status_check only; the first component otherwise), and at most component_limit per vendor. Present in detailed mode only."
},
"statuspage_url": {
"type": "string",
"description": "Status page base URL used for this vendor."
},
"active_incidents": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"name",
"impact",
"status",
"latest_update"
],
"properties": {
"id": {
"type": "string",
"description": "Unique incident identifier from the vendor's status API."
},
"name": {
"type": "string",
"description": "Incident title."
},
"impact": {
"enum": [
"none",
"minor",
"major",
"critical",
"maintenance"
],
"type": "string",
"description": "Severity level: none = informational, minor = degraded performance, major = partial outage, critical = full outage, maintenance = scheduled window folded into incident history."
},
"status": {
"type": "string",
"description": "Current incident status (e.g., investigating, monitoring, resolved)."
},
"started_at": {
"type": [
"string",
"null"
],
"description": "ISO 8601 timestamp, with the vendor's UTC offset (Z, +00:00, or a local offset such as -07:00), when the incident started, or null/absent if not set by the vendor."
},
"latest_update": {
"type": "string",
"description": "Most recent update text, as plain text: HTML markup the vendor published is converted, and any other < is text the vendor wrote."
}
},
"description": "An active incident entry.",
"additionalProperties": false
},
"description": "Active (non-resolved) incidents."
},
"degraded_components": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"group",
"status"
],
"properties": {
"name": {
"type": "string",
"description": "Component name as the status page publishes it — the leaf alone, without its group. Several leaves can share a name (one per region or product); group tells them apart."
},
"group": {
"type": [
"string",
"null"
],
"description": "Name of the group the status page files this component under — typically the product or region it belongs to — or null when it is not in a group."
},
"status": {
"enum": [
"degraded_performance",
"partial_outage",
"major_outage",
"under_maintenance"
],
"type": "string",
"description": "Degradation level: degraded_performance = slow/intermittent, partial_outage = some requests failing, major_outage = most requests failing, under_maintenance = scheduled maintenance in progress."
}
},
"description": "A degraded component entry.",
"additionalProperties": false
},
"description": "Every component not in an operational state, uncapped — a vendor with a large edge-node fleet routinely publishes dozens. Includes in-progress maintenance windows (status under_maintenance) alongside genuine outages; read status to tell a planned window from a fault. Empty when all clear."
},
"all_components_total": {
"type": "number",
"description": "Components matching component_filter for this vendor, before component_offset and component_limit — the length of the whole list all_components is a page of. Present in detailed mode only."
},
"next_component_offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Where this vendor's component list continues. Present in detailed mode only, and only when components remain past the returned page: pass it as component_offset to devops_status_check, with this vendor, mode \"detailed\", and the same component_filter. Absent on the last page."
},
"scheduled_maintenances": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"scheduled_for",
"scheduled_until",
"status"
],
"properties": {
"name": {
"type": "string",
"description": "Maintenance window name."
},
"status": {
"type": "string",
"description": "Maintenance status (scheduled, in_progress, completed)."
},
"scheduled_for": {
"type": "string",
"description": "ISO 8601 start time, with the vendor's UTC offset."
},
"scheduled_until": {
"type": [
"string",
"null"
],
"description": "ISO 8601 end time, with the vendor's UTC offset, or null when the vendor's feed publishes no planned end."
}
},
"description": "A scheduled maintenance entry.",
"additionalProperties": false
},
"description": "Upcoming or in-progress maintenance windows. Present in detailed mode only."
}
},
"description": "Status result for a single vendor.",
"additionalProperties": false
},
"description": "Per-vendor status results for the vendors checked, in the same order as the input vendors list."
},
"summary": {
"type": "object",
"required": [
"total",
"operational",
"degraded",
"down",
"maintenance",
"unavailable"
],
"properties": {
"down": {
"type": "number",
"description": "Vendors rated critical."
},
"total": {
"type": "number",
"description": "Total number of vendors checked — never counts deferred_vendors."
},
"degraded": {
"type": "number",
"description": "Vendors rated minor or major."
},
"maintenance": {
"type": "number",
"description": "Vendors rated maintenance — in a scheduled window the vendor published, with no open incident rated minor or worse. Counted apart from degraded and down, which are faults."
},
"operational": {
"type": "number",
"description": "Vendors rated none — indicator none and no open incident rated minor or worse — and not errored."
},
"unavailable": {
"type": "number",
"description": "Vendors that could not be checked (carry an error) — unresolvable slug, blocked target, or failed status fetch. Counted as unknown, never operational."
}
},
"description": "Aggregate health counts across all checked vendors. Each vendor is rated by the worse of its indicator and its worst open incident rated minor or worse; an incident rated none or maintenance never raises the rating. Buckets partition the batch: operational + degraded + down + maintenance + unavailable = total.",
"additionalProperties": false
},
"truncated": {
"type": "boolean",
"description": "True when at least one vendor has components past the returned page — those vendors carry next_component_offset. Absent otherwise, including on the last page of a list."
},
"totalCount": {
"type": "number",
"description": "Components matching component_filter across all vendors, before component_offset and the cap. Present only when truncated."
},
"deferred_vendors": {
"type": "array",
"items": {
"type": "string",
"description": "A vendor entry exactly as provided."
},
"description": "Entries past the first 20 in vendors, verbatim and in input order. They were not checked; resend them in another call. Empty when every entry was checked."
},
"nextToolSuggestions": {
"type": "array",
"items": {
"type": "object",
"required": [
"toolName",
"reason",
"args"
],
"properties": {
"args": {
"type": "object",
"description": "Ready-to-use devops_suggest_action arguments: vendor (registry slug, or the normalized status page URL for a raw URL), vendor_indicator (only for minor, major, or critical), affected_components (degraded components outside a maintenance window, each written \"Group / Leaf\" when it is in a group), incident_summary (title of the most recently started open incident rated minor or worse).",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"reason": {
"type": "string",
"description": "Why the vendor qualifies: its reported indicator, or the open incident behind it."
},
"toolName": {
"type": "string",
"description": "Tool to call next — \"devops_suggest_action\"."
}
},
"description": "A recommended follow-up tool call with pre-filled arguments.",
"additionalProperties": false
},
"description": "One devops_suggest_action call per vendor with an active problem — an indicator of minor, major, or critical, or an open incident of that impact even while the indicator reads none or maintenance; these are the vendors summary counts as degraded or down — with its arguments filled from that vendor's result. Vendors that could not be checked never appear. Empty when no checked vendor has an active problem."
}
},
"additionalProperties": false
}devops_status_check annotations
{
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}devops_get_incidents — Devops Get Incidents
Advertised read-onlyOpen-world
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 maintenance windows: upcoming and in-progress ones, plus completed ones on Atlassian Statuspage, Firehydrant, and Datadog vendors (Status.io vendors list upcoming and in-progress only). Narrow further with match (terms in the title or affected component names, plus location names and IDs on Google Cloud and AWS) and since/until (a start-date range) — all applied before paging, so totals count only what they keep. Page through long histories with limit + offset — a truncated result discloses the total and returns the value to page with in nextOffset. Each response is held to 64,000 bytes per surface: a page can stop short of limit at that budget (the paging fields and notice say so), and an incident too large on its own keeps only its newest updates, with updates_omitted counting the rest — full_updates: true returns them all. Some vendor feeds cap their own history: when upstreamCeiling is present the vendor API returned everything it will serve, and older incidents are not reachable at a higher offset; the notice says whether since reaches them. On Atlassian Statuspage vendors, since (a date) also reads the status page's quarterly history archive back to that date, or 24 months back at most, where the page publishes one — not on a vendor that covers only part of a shared page, such as "sendgrid"; those records are marked source: "history" and carry the title, impact, start and end times, and final update message only. An empty result, or a history read that stopped short of since, explains itself in notice.
devops_get_incidents input schema
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"vendor"
],
"properties": {
"limit": {
"type": "integer",
"default": 20,
"maximum": 9007199254740991,
"minimum": 1,
"description": "Maximum incidents to return per call, at least 1. A value over 50 is served as 50, and the notice says so. Page through longer history with offset rather than raising this."
},
"match": {
"type": "string",
"maxLength": 200,
"description": "Terms to look for, separated by spaces, in each incident's title, its affected component names, and, on Google Cloud and AWS, its affected location names and IDs (\"us-central1\", \"me-south-1\", \"bahrain\"), ignoring case. An incident is kept when every term appears in its title, one of its component names, or one of its location names or IDs, each term on its own. A one-word term matches all or part of a word. A term whose words are joined by punctuation (\"eu-central-1\", \"git-operations\", \"git/operations\") matches only where those words appear together, in that order, within one of those texts, anywhere in it: \"eu-central-1\" finds eu-central-1 but not me-central-1, and \"eu-west\" finds every eu-west region. History-archive records, and vendors that publish no components, match on title alone. Applied before limit/offset, so totals and paging count only the matches. Leave blank to keep every incident."
},
"since": {
"anyOf": [
{
"type": "string",
"const": ""
},
{
"type": "string",
"format": "date",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
"description": "Earliest start date to include, as YYYY-MM-DD (UTC), e.g. \"2025-10-01\"."
}
],
"description": "Earliest start date to include, as YYYY-MM-DD (UTC). Accepted with filter \"all\" or \"resolved\". A record's start is its scheduled_for, else the earlier of its started_at and created_at; records that started before since are left out, and limit/offset page the rest. On Atlassian Statuspage vendors it also reads the status page's quarterly history archive back to this date, reaching incidents older than the 50 the status API serves — except on a vendor that covers only part of a shared status page (such as \"sendgrid\" on Twilio's page), whose archive records carry no components to narrow by. The archive is read back 24 months at most: for an earlier date, older records come only from what the status API still returns (such as completed maintenance windows), and the notice gives the date the archive was read back to. On a vendor with no archive this tool reads, since filters only what its status feed returns. Where that feed is a recent window, a since earlier than the oldest record it returned gets that record's start date in the notice. A feed that carries its page's whole history (such as \"redis-cloud\" or \"datadog\") holds nothing older, so it gets that date only on an empty result whose until is earlier than it. Omit to read only the status API."
},
"until": {
"anyOf": [
{
"type": "string",
"const": ""
},
{
"type": "string",
"format": "date",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
"description": "Latest start date to include, as YYYY-MM-DD (UTC), e.g. \"2025-10-31\"."
}
],
"description": "Latest start date to include, as YYYY-MM-DD (UTC) — the whole day, so until equal to since returns that one day. Accepted with filter \"all\" or \"resolved\", and on or after since. A record's start is its scheduled_for, else the earlier of its started_at and created_at; records that started after until are left out before limit/offset page the rest. It reads no history archive on its own: set since as well to reach incidents older than the status API returns, through an archive read back 24 months at most. On a vendor with no archive this tool reads, until alone filters what its status feed returns. Where that feed is a recent window, the notice then gives the start date of the oldest record it returned. A feed that carries its page's whole history (such as \"redis-cloud\" or \"datadog\") gets that date only on an empty result whose until is earlier than it."
},
"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 maintenance windows — upcoming and in-progress ones, plus completed ones on Atlassian Statuspage, Firehydrant (\"redis-cloud\"), and Datadog (\"datadog\", \"datadog-eu1\") vendors; Status.io vendors (\"gitlab\", \"neon\") list upcoming and in-progress windows only. Not every vendor backend serves every filter — \"aws\" lists a resolved event only until it drops off its feed, \"azure\" lists open items only (never resolved), and \"aws\", \"azure\", \"azure-devops\", \"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."
},
"full_updates": {
"type": "boolean",
"default": false,
"description": "Return every update of an incident that is too large for the response size budget on its own, instead of only its newest updates. Default false. Pair it with limit: 1 and the offset the notice names; the response can then run past the budget."
}
},
"additionalProperties": false
}devops_get_incidents output schema
{
"type": "object",
"anyOf": [
{
"not": {
"required": [
"error"
]
},
"required": [
"vendor",
"name",
"incidents",
"total_returned",
"statuspage_url"
]
},
{
"required": [
"error"
]
}
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"cap": {
"type": "number",
"description": "The limit that was applied: the requested limit, or 50 when a larger one was requested. Present only when truncated."
},
"name": {
"type": "string",
"description": "Display name of the vendor."
},
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "JSON-RPC error code for this failure."
},
"data": {
"type": "object",
"properties": {
"reason": {
"type": "string",
"examples": [
"vendor_not_found",
"target_blocked",
"invalid_since",
"invalid_until",
"statuspage_unavailable"
],
"description": "Machine-readable failure mode. Declared by this tool: `vendor_not_found`: Vendor slug not in registry and input is not a valid URL. `target_blocked`: A raw URL resolves to a private, loopback, or cloud-metadata address. `invalid_since`: since was passed with filter \"active\" or \"scheduled\". `invalid_until`: until was passed with filter \"active\" or \"scheduled\", or names a date earlier than the since date. `statuspage_unavailable`: The vendor's status API returned an error or timed out. Other values are possible when a failure originates below the handler."
},
"recovery": {
"type": "object",
"required": [
"hint"
],
"properties": {
"hint": {
"type": "string"
}
},
"description": "Actionable next step for the caller.",
"additionalProperties": {}
},
"retryable": {
"type": "boolean",
"description": "Whether retrying may succeed."
}
},
"additionalProperties": {}
},
"message": {
"type": "string",
"description": "Human-readable description of what went wrong."
}
},
"description": "Present when the call failed. Absent on success.",
"additionalProperties": {}
},
"shown": {
"type": "number",
"description": "Number of incidents on this page: the limit, or fewer when the page stopped at the response size budget. Present only when truncated."
},
"notice": {
"type": "string",
"description": "Plain-language explanation of this result — a limit over 50 that was served as 50 (with the requested and effective values), a since older than the 24-month history-archive floor (with the date the archive was read back to), a since earlier than the oldest record a vendor feed that is a recent window with no history archive behind it returned, or an until without since on such a feed (with that record's start date), how to page onward, that the page stopped at the response size budget or left out an oversized incident's oldest updates (and the call that returns them all), why it came back empty (the vendor currently publishes nothing at all, a capped feed of a shared status page that returned nothing touching the vendor's components, a filter the backend cannot satisfy, an offset past the end, a since/until range or match terms that left everything out — naming the archive floor when the range reaches back past it, and where a feed that carries its page's whole history starts when the range ends before that), that the vendor feed capped the history (and whether since reaches past that cap), or how far the history archive was read when it stopped short of since or its floor. On a vendor that reads an umbrella status page with no components, such as \"atlassian\", its last sentence names the product slugs to check instead. Absent when the result needs no explanation."
},
"vendor": {
"type": "string",
"description": "Vendor slug or URL as provided."
},
"incidents": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"name",
"impact",
"status",
"created_at",
"resolved_at",
"scheduled_for",
"scheduled_until",
"duration_minutes",
"affected_components",
"updates",
"source"
],
"properties": {
"id": {
"type": "string",
"description": "Unique incident identifier from the vendor's status API."
},
"name": {
"type": "string",
"description": "Incident title."
},
"impact": {
"enum": [
"none",
"minor",
"major",
"critical",
"maintenance"
],
"type": "string",
"description": "Severity level: none = informational, minor = degraded performance, major = partial outage, critical = full outage, maintenance = scheduled window."
},
"source": {
"enum": [
"api",
"history"
],
"type": "string",
"description": "Where this record came from. api: the vendor's status API, with the full update timeline and affected components. history: the status page's quarterly history archive, read only when since is set — title, impact, start and end times, and the final update message, with no components and no started_at, scheduled window, or duration."
},
"status": {
"type": "string",
"description": "Current status: investigating | identified | monitoring | resolved | postmortem | scheduled | in_progress | completed | unknown. unknown marks a history-archive record with no end time, whose lifecycle stage the archive does not publish."
},
"updates": {
"type": "array",
"items": {
"type": "object",
"required": [
"status",
"body",
"created_at"
],
"properties": {
"body": {
"type": "string",
"description": "Update text from the vendor, as plain text: HTML markup the vendor published is converted (a link reads as its text, then its URL), and any other < is text the vendor wrote."
},
"status": {
"type": "string",
"description": "Incident status at the time of this update."
},
"created_at": {
"type": "string",
"description": "ISO 8601 timestamp of this update, with the vendor's UTC offset."
}
},
"description": "A single status update from the vendor.",
"additionalProperties": false
},
"description": "Chronological list of incident updates (oldest first). A history-archive record carries only its final update, dated at its end time (or its start when it has none). An incident too large for the response size budget on its own carries only its newest updates, and updates_omitted counts the rest."
},
"shortlink": {
"type": [
"string",
"null"
],
"description": "Direct URL to the incident page, or null/absent if not provided by the vendor."
},
"created_at": {
"type": "string",
"description": "ISO 8601 timestamp when the incident was created, carrying the UTC offset the vendor published (Z, +00:00, or a local offset such as -07:00). For a history-archive record, the start time its status page displays, to the minute, in UTC."
},
"started_at": {
"type": [
"string",
"null"
],
"description": "ISO 8601 timestamp, with the vendor's UTC offset, when the incident started, or null/absent if not set by the vendor."
},
"resolved_at": {
"type": [
"string",
"null"
],
"description": "ISO 8601 timestamp, with the vendor's UTC offset, when resolved, or null if still active. For a history-archive record, to the minute, in UTC."
},
"scheduled_for": {
"type": [
"string",
"null"
],
"description": "Present for scheduled maintenances — ISO 8601 start time with the vendor's UTC offset."
},
"scheduled_until": {
"type": [
"string",
"null"
],
"description": "Present for scheduled maintenances — ISO 8601 end time with the vendor's UTC offset, or null when the vendor's feed publishes no planned end."
},
"updates_omitted": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "How many of this incident's oldest updates were left out because it alone exceeds the response size budget; the updates returned are its newest. Absent when every update is returned. Call again with full_updates: true and limit: 1 at this incident's offset to read them all."
},
"duration_minutes": {
"type": [
"number",
"null"
],
"description": "Minutes from started_at to resolved_at. Null for active or scheduled incidents, or when the vendor-authored timestamps are missing, invalid, or inverted."
},
"affected_locations": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"name",
"current"
],
"properties": {
"id": {
"type": "string",
"description": "Provider location ID, e.g. \"us-central1\"."
},
"name": {
"type": "string",
"description": "Provider location name, e.g. \"Iowa (us-central1)\"."
},
"current": {
"type": "boolean",
"description": "True while the incident still affects this location; false once it has stopped affecting it."
}
},
"description": "A location the incident lists.",
"additionalProperties": false
},
"description": "Regions the incident lists, currently affected first: on Google Cloud its regions and multi-regions, on AWS the one region its event names (\"global\" for a global service); absent when it lists none."
},
"affected_components": {
"type": "array",
"items": {
"type": "string"
},
"description": "Component names affected by this incident."
}
},
"description": "An incident or scheduled maintenance entry.",
"additionalProperties": false
},
"description": "Matching incidents."
},
"truncated": {
"type": "boolean",
"description": "True when more incidents matched than this page returned — because of limit, or because the page stopped at the response size budget. Absent when this page reached the end of the matches."
},
"nextOffset": {
"type": "number",
"description": "The offset to pass on the next call to continue from where this page stopped, already computed as offset + the number returned. Present only when truncated — its absence means this page reached the end of what the filter matched."
},
"totalCount": {
"type": "number",
"description": "Total incidents matching the filter, date range, and match, across all pages, before offset/limit windowing. Present only when the result was truncated."
},
"statuspage_url": {
"type": "string",
"description": "Status page base URL used."
},
"total_returned": {
"type": "number",
"description": "Number of incidents in the response."
},
"upstreamCeiling": {
"type": "number",
"description": "Maximum incidents the vendor's own status API serves in one fetch, present only when that ceiling was reached on this call. It bounds the history independently of limit and offset: incidents older than the oldest one returned cannot be fetched at any offset. On Atlassian Statuspage vendors, since reads past it from the page's history archive, except on a vendor that covers only part of a shared page, such as \"sendgrid\"; the notice says whether since reaches past it on this call. Absent when the vendor feed is unbounded, returned less than its ceiling, or since was set and the history archive was read back to it (or to its 24-month floor, when since is older)."
}
},
"additionalProperties": false
}devops_get_incidents annotations
{
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}devops_watch_stack — Devops Watch Stack
Open-world
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; a shared deployment that does not authenticate callers saves nothing, so there vendors is required on every call and the response says so. Up to 20 vendors are saved per stack and checked per call; use several stack names for a larger set. 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. Every vendor with an active problem gets a pre-filled devops_suggest_action call in nextToolSuggestions. Ideal for morning status checks or pre-deploy sweeps. Multiple stacks can coexist (e.g., "production", "staging").
devops_watch_stack input schema
{
"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."
},
"maxItems": 100,
"description": "Vendor slugs (e.g., \"github\", \"aws\") or raw Atlassian Statuspage base URLs. When provided, saves this list as the stack where stacks are saved; a list longer than 20 is then rejected and nothing is saved. When omitted, uses the previously saved list for stack_name; required on every call on a deployment that does not authenticate callers, which saves no stacks — there the first 20 are checked and the rest return in deferred_vendors. Lists longer than 100 are rejected."
},
"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": 9007199254740991,
"minimum": 1,
"description": "Maximum components returned per vendor in detailed mode, at least 1. A value above 500 is reduced to 500, and notice says so. 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 and their group names in detailed mode (e.g., \"api\" to check just the API components, or a product or region a page groups components under). Applied before component_limit, so it reaches a specific component the cap would otherwise omit; a capped vendor's full list continues in devops_status_check from its next_component_offset. A filter that matches nothing for a vendor is reported in notice. Ignored in summary mode."
}
},
"additionalProperties": false
}devops_watch_stack output schema
{
"type": "object",
"anyOf": [
{
"not": {
"required": [
"error"
]
},
"required": [
"stack_name",
"health",
"summary",
"vendors",
"deferred_vendors",
"stack_persisted",
"omitted_vendors",
"checked_at",
"nextToolSuggestions"
]
},
{
"required": [
"error"
]
}
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"cap": {
"type": "number",
"description": "The per-vendor component_limit that was applied. Present only when truncated."
},
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "JSON-RPC error code for this failure."
},
"data": {
"type": "object",
"properties": {
"reason": {
"type": "string",
"examples": [
"no_stack",
"vendors_required",
"stack_too_large",
"vendor_not_found",
"target_blocked"
],
"description": "Machine-readable failure mode. Declared by this tool: `no_stack`: No vendors provided and no saved stack found for stack_name. `vendors_required`: No vendors provided on a deployment that saves no stacks because callers are not authenticated. `stack_too_large`: More than 20 vendors were provided on a deployment that saves stacks, so nothing was saved. `vendor_not_found`: No vendor in the stack could be checked and the first failure was a slug that is not in the registry and is not a valid URL. `target_blocked`: No vendor in the stack could be checked and the first failure was a raw URL resolving to a private, loopback, or cloud-metadata address. Other values are possible when a failure originates below the handler."
},
"recovery": {
"type": "object",
"required": [
"hint"
],
"properties": {
"hint": {
"type": "string"
}
},
"description": "Actionable next step for the caller.",
"additionalProperties": {}
},
"retryable": {
"type": "boolean",
"description": "Whether retrying may succeed."
}
},
"additionalProperties": {}
},
"message": {
"type": "string",
"description": "Human-readable description of what went wrong."
}
},
"description": "Present when the call failed. Absent on success.",
"additionalProperties": {}
},
"shown": {
"type": "number",
"description": "Components returned across the stack. Present only when truncated."
},
"health": {
"enum": [
"all_operational",
"maintenance",
"degraded",
"partial_outage",
"major_outage",
"unknown"
],
"type": "string",
"description": "Aggregate health rollup over each checked vendor's rating — the worse of its indicator and its worst open incident rated minor or worse — taking the worst rung that applies: major_outage = a vendor rated critical, partial_outage = a vendor rated major, degraded = a vendor rated minor, unknown = at least one vendor could not be checked (unresolvable entry, blocked target, or failed fetch) and none rated worse, maintenance = a vendor in a scheduled window and nothing worse, all_operational = every vendor checked and rated none. Never all_operational when any vendor errored, is in a window, or has an open incident rated minor or worse."
},
"notice": {
"type": "string",
"description": "Plain-language explanation of what this call left out or adjusted, in this order: vendors past the first 20 (listed in deferred_vendors), and for a saved stack how to sweep every one; a component_limit above 500 reduced to 500; in detailed mode, how many components the cap omitted and how to reach them (devops_status_check with that vendor and its next_component_offset as component_offset, component_filter to target one, or component_limit to raise a cap below 500), and which checked vendors component_filter matched no component of, with how many each publishes; and last, for a vendor whose entry reads an umbrella status page with no components (atlassian), the slugs of the entries reading its product pages. Present only when one of these applies."
},
"summary": {
"type": "object",
"required": [
"total",
"operational",
"degraded",
"down",
"maintenance",
"unavailable"
],
"properties": {
"down": {
"type": "number",
"description": "Vendors rated critical."
},
"total": {
"type": "number",
"description": "Total vendors checked on this call — never counts deferred_vendors."
},
"degraded": {
"type": "number",
"description": "Vendors rated minor or major."
},
"maintenance": {
"type": "number",
"description": "Vendors rated maintenance — in a scheduled window the vendor published, with no open incident rated minor or worse. Counted apart from degraded and down, which are faults."
},
"operational": {
"type": "number",
"description": "Vendors rated none — indicator none and no open incident rated minor or worse — and not errored."
},
"unavailable": {
"type": "number",
"description": "Vendors that could not be checked (carry an error) — unresolvable entry, blocked target, or failed status fetch. Counted as unknown, never operational."
}
},
"description": "Aggregate health counts across all checked vendors. Each vendor is rated by the worse of its indicator and its worst open incident rated minor or worse; an incident rated none or maintenance never raises the rating. Buckets partition the stack: operational + degraded + down + maintenance + unavailable = total.",
"additionalProperties": false
},
"vendors": {
"type": "array",
"items": {
"type": "object",
"required": [
"vendor",
"name",
"indicator",
"description",
"degraded_components",
"active_incidents",
"cached",
"checked_at",
"statuspage_url"
],
"properties": {
"name": {
"type": "string",
"description": "Display name of the vendor."
},
"error": {
"type": "string",
"description": "Why this vendor could not be checked — unreachable status API, timeout, non-2xx, or a response that is not a Statuspage payload. Reported here rather than thrown so one bad vendor does not fail the batch. Absent when the vendor was fetched successfully."
},
"cached": {
"type": "boolean",
"description": "True when this result was served from the in-memory status cache, shared across callers (60 s TTL by default), so its data can be up to that TTL older than checked_at."
},
"vendor": {
"type": "string",
"description": "Vendor slug or URL as provided."
},
"indicator": {
"enum": [
"none",
"minor",
"major",
"critical",
"maintenance"
],
"type": "string",
"description": "Overall health indicator, as the vendor published it: none = no degradation reported, minor = some degradation, major = significant outage, critical = complete outage, maintenance = scheduled window in progress, planned rather than a fault. A page can rate it from component statuses alone, so it can read none or maintenance while active_incidents lists an open incident rated minor or worse; summary, and devops_watch_stack's health, rate the vendor by the worse of the two."
},
"checked_at": {
"type": "string",
"description": "ISO 8601 UTC timestamp of this check — when this result was built, not when the status data was fetched; see cached."
},
"description": {
"type": "string",
"description": "Human-readable status description (e.g., \"All Systems Operational\")."
},
"all_components": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"group",
"status",
"description"
],
"properties": {
"name": {
"type": "string",
"description": "Component name as the status page publishes it — the leaf alone, without its group. Several leaves can share a name (one per region or product); group tells them apart."
},
"group": {
"type": [
"string",
"null"
],
"description": "Name of the group the status page files this component under — typically the product or region it belongs to — or null when it is not in a group."
},
"status": {
"type": "string",
"description": "Component operational status."
},
"description": {
"type": [
"string",
"null"
],
"description": "Component description, or null if not provided."
}
},
"description": "A component entry.",
"additionalProperties": false
},
"description": "Components including operational ones, narrowed by component_filter (matched against name and group) when given, starting at component_offset (devops_status_check only; the first component otherwise), and at most component_limit per vendor. Present in detailed mode only."
},
"statuspage_url": {
"type": "string",
"description": "Status page base URL used for this vendor."
},
"active_incidents": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"name",
"impact",
"status",
"latest_update"
],
"properties": {
"id": {
"type": "string",
"description": "Unique incident identifier from the vendor's status API."
},
"name": {
"type": "string",
"description": "Incident title."
},
"impact": {
"enum": [
"none",
"minor",
"major",
"critical",
"maintenance"
],
"type": "string",
"description": "Severity level: none = informational, minor = degraded performance, major = partial outage, critical = full outage, maintenance = scheduled window folded into incident history."
},
"status": {
"type": "string",
"description": "Current incident status (e.g., investigating, monitoring, resolved)."
},
"started_at": {
"type": [
"string",
"null"
],
"description": "ISO 8601 timestamp, with the vendor's UTC offset (Z, +00:00, or a local offset such as -07:00), when the incident started, or null/absent if not set by the vendor."
},
"latest_update": {
"type": "string",
"description": "Most recent update text, as plain text: HTML markup the vendor published is converted, and any other < is text the vendor wrote."
}
},
"description": "An active incident entry.",
"additionalProperties": false
},
"description": "Active (non-resolved) incidents."
},
"degraded_components": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"group",
"status"
],
"properties": {
"name": {
"type": "string",
"description": "Component name as the status page publishes it — the leaf alone, without its group. Several leaves can share a name (one per region or product); group tells them apart."
},
"group": {
"type": [
"string",
"null"
],
"description": "Name of the group the status page files this component under — typically the product or region it belongs to — or null when it is not in a group."
},
"status": {
"enum": [
"degraded_performance",
"partial_outage",
"major_outage",
"under_maintenance"
],
"type": "string",
"description": "Degradation level: degraded_performance = slow/intermittent, partial_outage = some requests failing, major_outage = most requests failing, under_maintenance = scheduled maintenance in progress."
}
},
"description": "A degraded component entry.",
"additionalProperties": false
},
"description": "Every component not in an operational state, uncapped — a vendor with a large edge-node fleet routinely publishes dozens. Includes in-progress maintenance windows (status under_maintenance) alongside genuine outages; read status to tell a planned window from a fault. Empty when all clear."
},
"all_components_total": {
"type": "number",
"description": "Components matching component_filter for this vendor, before component_offset and component_limit — the length of the whole list all_components is a page of. Present in detailed mode only."
},
"next_component_offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Where this vendor's component list continues. Present in detailed mode only, and only when components remain past the returned page: pass it as component_offset to devops_status_check, with this vendor, mode \"detailed\", and the same component_filter. Absent on the last page."
},
"scheduled_maintenances": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"scheduled_for",
"scheduled_until",
"status"
],
"properties": {
"name": {
"type": "string",
"description": "Maintenance window name."
},
"status": {
"type": "string",
"description": "Maintenance status (scheduled, in_progress, completed)."
},
"scheduled_for": {
"type": "string",
"description": "ISO 8601 start time, with the vendor's UTC offset."
},
"scheduled_until": {
"type": [
"string",
"null"
],
"description": "ISO 8601 end time, with the vendor's UTC offset, or null when the vendor's feed publishes no planned end."
}
},
"description": "A scheduled maintenance entry.",
"additionalProperties": false
},
"description": "Upcoming or in-progress maintenance windows. Present in detailed mode only."
}
},
"description": "Status result for a single vendor.",
"additionalProperties": false
},
"description": "Per-vendor status results for the vendors checked, in stack order."
},
"truncated": {
"type": "boolean",
"description": "True when at least one vendor's component list was capped at component_limit — those vendors carry next_component_offset. Absent when nothing was capped."
},
"checked_at": {
"type": "string",
"description": "ISO 8601 UTC timestamp of this check."
},
"stack_name": {
"type": "string",
"description": "Name of the stack checked."
},
"totalCount": {
"type": "number",
"description": "Components matching component_filter across the stack before the cap. Present only when truncated."
},
"omitted_vendors": {
"type": "array",
"items": {
"type": "string",
"description": "A vendor entry that cannot be part of a usable stack."
},
"description": "Entries that could not be resolved or whose URL was blocked; they still appear in vendors[] with an error. A call that saved the stack left them out of the write; a call that reused a saved stack leaves them in it until you re-provide the vendors list. Empty when every entry resolved."
},
"stack_persisted": {
"type": "boolean",
"description": "True when the vendor list was saved on this call. Only the vendors that resolved are saved — see omitted_vendors. Always false on a deployment that does not authenticate callers, which saves no stacks (persistence_notice says so)."
},
"deferred_vendors": {
"type": "array",
"items": {
"type": "string",
"description": "A vendor entry exactly as provided or saved."
},
"description": "Entries past the first 20, verbatim and in order, that were not checked on this call: the rest of a passed vendors list on a deployment that saves no stacks, or of a saved stack holding more than 20. Resend them in another call. Empty when every entry was checked."
},
"persistence_notice": {
"type": "string",
"description": "Present when this deployment saves no stacks because callers are not authenticated: nothing was saved, and vendors must be passed on every call."
},
"nextToolSuggestions": {
"type": "array",
"items": {
"type": "object",
"required": [
"toolName",
"reason",
"args"
],
"properties": {
"args": {
"type": "object",
"description": "Ready-to-use devops_suggest_action arguments: vendor (registry slug, or the normalized status page URL for a raw URL), vendor_indicator (only for minor, major, or critical), affected_components (degraded components outside a maintenance window, each written \"Group / Leaf\" when it is in a group), incident_summary (title of the most recently started open incident rated minor or worse).",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"reason": {
"type": "string",
"description": "Why the vendor qualifies: its reported indicator, or the open incident behind it."
},
"toolName": {
"type": "string",
"description": "Tool to call next — \"devops_suggest_action\"."
}
},
"description": "A recommended follow-up tool call with pre-filled arguments.",
"additionalProperties": false
},
"description": "One devops_suggest_action call per vendor with an active problem — an indicator of minor, major, or critical, or an open incident of that impact even while the indicator reads none or maintenance; these are the vendors summary counts as degraded or down — with its arguments filled from that vendor's result. Vendors that could not be checked never appear. Empty when no checked vendor has an active problem."
}
},
"additionalProperties": false
}devops_watch_stack annotations
{
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}devops_check_certs — Devops Check Certs
Advertised read-onlyOpen-world
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 — a server offering only those is still inspected), cipher suite, and HSTS presence when the port answers HTTP. 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". Non-HTTP TLS ports (IMAPS 993, SMTPS 465, DNS over TLS 853) are graded the same way, with HSTS reported as not checked. If a domain fails to connect at all, check devops_check_dns first — the name may not resolve. When a certificate fails to issue or renew, run devops_check_dns with record_types ["CAA"] to see which certificate authorities the domain allows.
devops_check_certs input schema
{
"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 for entries that do not carry their own. Defaults to 443. Use 8443 or custom ports for non-standard HTTPS endpoints, or 993, 465, 853, and the like for other TLS services. A port written on an entry (\"example.com:8443\") wins for that entry."
},
"domains": {
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"description": "A host to inspect: a hostname (\"api.github.com\"), an IP address, a host with a port (\"example.com:8443\", \"[2606:4700:4700::1111]:853\"), or a URL (\"https://example.com/login\"), which is reduced to its host."
},
"maxItems": 100,
"minItems": 1,
"description": "Hosts to inspect. The first 10 entries are inspected; up to 100 are accepted, and entries past the 10th come back uninspected and verbatim in deferred_domains, to resend in another call. Each entry is read as one host: surrounding whitespace and letter case are ignored, a scheme, path, query, or fragment is dropped, an internationalized name is converted to its ASCII form (\"münchen.de\" → \"xn--mnchen-3ya.de\"), and a port written on the entry is used for that entry in place of \"port\". An entry with no single host — a user name before \"@\", a bad port, or a malformed label — gets its own result with status \"error\" and is never connected to; the other entries still run."
},
"timeout_ms": {
"type": "integer",
"default": 5000,
"maximum": 9007199254740991,
"minimum": 1000,
"description": "Time limit in milliseconds for each domain, covering the connection, the handshake, a second handshake with TLS 1.0/1.1 enabled when the server offers nothing newer, and the HSTS request. A port that completes the handshake and then sends nothing is reported at this limit, certificate included. At least 1000; a value over 15000 is served as 15000, and the notice says so. Defaults to 5000 unless the server is configured otherwise. Increase for slow or geographically distant endpoints."
}
},
"additionalProperties": false
}devops_check_certs output schema
{
"type": "object",
"anyOf": [
{
"not": {
"required": [
"error"
]
},
"required": [
"results",
"deferred_domains"
]
},
{
"required": [
"error"
]
}
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "JSON-RPC error code for this failure."
},
"data": {
"type": "object",
"properties": {
"reason": {
"type": "string",
"description": "Machine-readable failure mode."
},
"recovery": {
"type": "object",
"required": [
"hint"
],
"properties": {
"hint": {
"type": "string"
}
},
"description": "Actionable next step for the caller.",
"additionalProperties": {}
},
"retryable": {
"type": "boolean",
"description": "Whether retrying may succeed."
}
},
"additionalProperties": {}
},
"message": {
"type": "string",
"description": "Human-readable description of what went wrong."
}
},
"description": "Present when the call failed. Absent on success.",
"additionalProperties": {}
},
"notice": {
"type": "string",
"description": "Present when the call was served at a bound: hosts past the per-call cap, named in deferred_domains, or a timeout_ms over 15000 that was served as 15000. Absent otherwise."
},
"results": {
"type": "array",
"items": {
"type": "object",
"required": [
"domain",
"port",
"status",
"flags",
"cert",
"tls",
"checked_at",
"error"
],
"properties": {
"tls": {
"anyOf": [
{
"type": "object",
"required": [
"protocol",
"cipher"
],
"properties": {
"cipher": {
"type": "string",
"description": "Negotiated cipher suite name."
},
"protocol": {
"type": "string",
"description": "Negotiated TLS version, e.g., \"TLSv1.3\"."
}
},
"additionalProperties": false
},
{
"type": "null"
}
],
"description": "TLS session details, or null when no TLS handshake completed."
},
"cert": {
"anyOf": [
{
"type": "object",
"required": [
"subject",
"san",
"issuer",
"valid_from",
"valid_until",
"days_until_expiry",
"chain_depth",
"chain_depth_unavailable_reason",
"hostname_verification_error",
"authorization_error",
"serial"
],
"properties": {
"san": {
"type": "array",
"items": {
"type": "string"
},
"description": "Subject Alternative Names covered by this certificate."
},
"issuer": {
"type": "string",
"description": "Issuer common name."
},
"serial": {
"type": "string",
"description": "Certificate serial number."
},
"subject": {
"type": "string",
"description": "Certificate subject CN."
},
"valid_from": {
"type": "string",
"description": "ISO 8601 UTC timestamp of certificate validity start."
},
"chain_depth": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "null"
}
],
"description": "Length of the certificate chain this runtime assembled from the leaf, counting the leaf: the certificates the server sent on the leaf's issuer path, then issuers from the runtime's own trust store, up to a self-signed certificate or one whose issuer was not found. It can include a root the server never sent, so it can differ from the number of certificates the server sent, and between runtimes. Null when no issuer for the leaf was found — read \"chain_depth_unavailable_reason\". Not a self-signed indicator or a trust verdict: use \"authorization_error\" for those."
},
"valid_until": {
"type": "string",
"description": "ISO 8601 UTC timestamp of certificate expiry."
},
"days_until_expiry": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Days remaining until certificate expiry. Negative = already expired."
},
"authorization_error": {
"type": [
"string",
"null"
],
"description": "OpenSSL chain-verification code when the certificate chain does not validate against the system trust store, or null when it validates. Common values: \"DEPTH_ZERO_SELF_SIGNED_CERT\" (self-signed leaf), \"SELF_SIGNED_CERT_IN_CHAIN\" / \"UNABLE_TO_VERIFY_LEAF_SIGNATURE\" (issuing root not trusted), \"CERT_HAS_EXPIRED\" (also reported in \"days_until_expiry\"). This is the authoritative chain-trust signal — the issuer and subject fields alone cannot detect an untrusted root."
},
"hostname_verification_error": {
"type": [
"string",
"null"
],
"description": "Node's hostname-verification message when the requested domain is not covered by the certificate's CN or SANs (e.g. \"Hostname/IP does not match certificate's altnames: …\"), or null when the hostname is covered. A non-null value means ordinary clients reject this certificate for this hostname; compare against the \"san\" list to see what it does cover."
},
"chain_depth_unavailable_reason": {
"type": [
"string",
"null"
],
"description": "Why \"chain_depth\" is null, or null when a depth was measured. A null depth means no issuer for the leaf was found among the certificates the server sent or in the trust store, as when a server sends its leaf without the certificate that issued it."
}
},
"additionalProperties": false
},
{
"type": "null"
}
],
"description": "Certificate details, or null when no certificate was retrieved (status \"error\")."
},
"port": {
"type": "number",
"description": "The port used for the TLS connection: the port written on the entry, otherwise the \"port\" input."
},
"error": {
"type": [
"string",
"null"
],
"description": "Why status is \"error\". Either no handshake completed — the entry has no single host (the message names the entry and the accepted shapes), the host was rejected as a private, loopback, or cloud-metadata target, a connection failure such as \"getaddrinfo ENOTFOUND …\" (for a server offering only TLS 1.0/1.1 that still refuses, the failure of the legacy-version attempt), or \"Timed out after 5000ms\" when timeout_ms ran out before a handshake completed — with cert and tls null and flags empty; or the handshake completed but the server presented no certificate, with cert null and the TLS session still reported in tls and flags. Null for every other status, including a completed handshake whose port never answered HTTP."
},
"flags": {
"type": "array",
"items": {
"type": "string"
},
"description": "Human-readable findings about the certificate and TLS session that were read: \"Expires in 12 days (warning)\", \"Certificate expired 40 days ago\", \"Hostname mismatch — the certificate does not cover api.example.com; clients will reject it\", \"Certificate chain not trusted (SELF_SIGNED_CERT_IN_CHAIN); clients will reject it\", \"Self-signed certificate\", \"Insecure TLS version in use: TLSv1.1\", and one HSTS finding: \"HSTS present\" or \"HSTS not configured\" when the port answered the HTTP request, or \"HSTS not checked — no HTTP response on port 993\" when it did not (a non-HTTP service such as IMAPS, SMTPS, or DNS over TLS). Empty when the connection never completed a handshake (rejected target, connection failure, or timeout) — the reason is in \"error\" only. A handshake that completed without a certificate keeps its TLS-session findings here alongside \"error\"."
},
"domain": {
"type": "string",
"description": "The host that was inspected, as read from the submitted entry (lowercase, ASCII, no scheme, port, or path; an IPv6 address without brackets). For an entry with no single host, the submitted string as given."
},
"status": {
"enum": [
"ok",
"warning",
"critical",
"error"
],
"type": "string",
"description": "Overall status. \"critical\" — the certificate expires in < 7 days or has already expired, the hostname is not covered by the certificate, chain verification failed (self-signed or untrusted root), or an insecure TLS version was negotiated (TLS 1.0/1.1, including a server that offers nothing newer); every one of these is rejected by ordinary clients. \"warning\" — expires in < 30 days. \"ok\" — none of the above. Graded from the certificate and session alone: HSTS never changes it, and neither does what the port sends after the handshake. \"error\" — no certificate was retrieved: the entry was rejected, the connection failed or timed out before the handshake completed, or the server presented no certificate; the reason is in \"error\"."
},
"checked_at": {
"type": "string",
"description": "ISO 8601 UTC timestamp of this check."
}
},
"description": "Certificate inspection result for one domain.",
"additionalProperties": false
},
"description": "Per-domain certificate inspection results."
},
"deferred_domains": {
"type": "array",
"items": {
"type": "string",
"description": "A submitted host entry, exactly as sent."
},
"description": "Host entries past the first 10, not inspected on this call, verbatim and in input order. Resend them in another call. Empty when every entry was inspected."
}
},
"additionalProperties": false
}devops_check_certs annotations
{
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}devops_check_dns — Devops Check Dns
Advertised read-onlyOpen-world
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 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.
devops_check_dns input schema
{
"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\", \"_dmarc.example.com\"). A URL or a host:port is reduced to its host."
},
"maxItems": 100,
"minItems": 1,
"description": "Domain names to query. The first 10 entries are queried; up to 100 are accepted, and entries past the 10th come back unqueried and verbatim in deferred_domains, to resend in another call. Each entry is read as one name: surrounding whitespace and letter case are ignored, a scheme, port, path, query, or fragment is dropped, and an internationalized name is converted to its ASCII form (\"münchen.de\" → \"xn--mnchen-3ya.de\"); a trailing dot and underscore labels are kept. An entry that is not a domain name — an IP address, a user name before \"@\", a bad port, or a malformed label — gets its own result with \"error\" set and is never queried; the other entries still run."
},
"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"
],
"maxItems": 20,
"description": "Resolver IP addresses to query. Defaults to Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9). An empty array uses the same defaults. Add custom resolvers to test resolver-specific behavior. A resolver listed more than once — the same address and port, however written (\"8.8.8.8\" and \"8.8.8.8:53\") — is queried once, under its first spelling. The first 5 distinct resolvers are queried; up to 20 entries are accepted, and the rest come back unqueried in deferred_resolvers, to resend with the same domains in another call. 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": 9007199254740991,
"minimum": 1000,
"description": "Time limit in milliseconds for each domain+resolver pair, covering every requested record type and any retry over TCP. A resolver that has not answered within it reports \"timeout\" for the unanswered types. At least 1000; a value over 10000 is served as 10000, and the notice says so. Defaults to 3000 unless the server is configured otherwise."
},
"record_types": {
"type": "array",
"items": {
"enum": [
"A",
"AAAA",
"CNAME",
"MX",
"TXT",
"NS",
"CAA",
"SOA"
],
"type": "string"
},
"default": [
"A",
"AAAA",
"MX",
"TXT"
],
"description": "DNS record types to resolve. Defaults to A, AAAA, MX, and TXT. An empty array uses the same defaults. A type listed more than once is queried once. Add NS to check nameserver delegation. Add CNAME when investigating redirect chains. Add CAA when a certificate will not issue or renew: it lists the certificate authorities allowed to issue for the name. CAA is reported for the exact name only; a CA that finds none there checks the parent domains, so no CAA at a subdomain does not mean any CA may issue. Add SOA to compare zone serials across resolvers. SOA answers only at a zone apex, so a name below it returns nodata (a name that is a CNAME returns the SOA of its target). A serial difference means a zone change has not reached every resolver only when those resolvers report the same primary nameserver; a different primary means more than one DNS provider serves the zone."
}
},
"additionalProperties": false
}devops_check_dns output schema
{
"type": "object",
"anyOf": [
{
"not": {
"required": [
"error"
]
},
"required": [
"results",
"deferred_domains",
"deferred_resolvers"
]
},
{
"required": [
"error"
]
}
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "JSON-RPC error code for this failure."
},
"data": {
"type": "object",
"properties": {
"reason": {
"type": "string",
"examples": [
"target_blocked"
],
"description": "Machine-readable failure mode. Declared by this tool: `target_blocked`: A resolver is a private, loopback, or otherwise non-public address, or is not an IP literal at all. Other values are possible when a failure originates below the handler."
},
"recovery": {
"type": "object",
"required": [
"hint"
],
"properties": {
"hint": {
"type": "string"
}
},
"description": "Actionable next step for the caller.",
"additionalProperties": {}
},
"retryable": {
"type": "boolean",
"description": "Whether retrying may succeed."
}
},
"additionalProperties": {}
},
"message": {
"type": "string",
"description": "Human-readable description of what went wrong."
}
},
"description": "Present when the call failed. Absent on success.",
"additionalProperties": {}
},
"notice": {
"type": "string",
"description": "Present when the call was served at a bound: domains or resolvers past the per-call cap, named in deferred_domains and deferred_resolvers, or a timeout_ms over 10000 that was served as 10000. Absent otherwise."
},
"results": {
"type": "array",
"items": {
"type": "object",
"required": [
"domain",
"records",
"records_source",
"resolver_results",
"propagation_discrepancies",
"flags",
"error"
],
"properties": {
"error": {
"type": [
"string",
"null"
],
"description": "Set only when the domain could not be queried at all: either the entry is not a domain name — rejected before any query, so \"resolver_results\" is empty, and the message names the entry and the accepted shapes — or every resolver failed and none returned records, in which case each failing resolver is named with its own outcome (\"8.8.8.8: SERVFAIL on A; 1.1.1.1: NXDOMAIN on A\") so a split result stays visible. Null when at least one resolver answered; per-resolver failures are still in \"resolver_results\" and \"flags\"."
},
"flags": {
"type": "array",
"items": {
"type": "string"
},
"description": "Human-readable observations that need attention: \"NXDOMAIN from 8.8.8.8, 1.1.1.1 on A, MX — the domain does not exist …\", \"Partial resolution on A records — 9.9.9.9 (nodata) returned nothing while 8.8.8.8 answered\", \"No MX records found\", \"CNAME detected — further records resolve via the CNAME target\". A value_variation disagreement is not flagged here — it is reported in \"propagation_discrepancies\" because it is normal for geo-steered domains. Empty for a domain rejected before any query, whose reason is in \"error\"."
},
"domain": {
"type": "string",
"description": "The domain name that was queried, as read from the submitted entry (lowercase, ASCII, no scheme, port, or path). For an entry that is not a domain name, the submitted string as given."
},
"records": {
"type": "object",
"description": "Resolved records from a single resolver, keyed by record type (A, AAAA, CNAME, MX, TXT, NS, CAA, SOA). Names carry no trailing dot; MX renders as \"<preference> <exchange>\", CAA as '<flags> <tag> \"<value>\"', and SOA as \"<primary nameserver> <hostmaster> <serial> <refresh> <retry> <expire> <minimum>\". Taken from the primary resolver (first in \"resolvers\"), or from the first resolver that returned records when the primary returned none. Read \"records_source\" for which resolver these came from, and \"resolver_results\" for the full per-resolver picture. This is also the reference set the per-resolver answers are reported against: a resolver that returned exactly these values for a type names it in \"records_same_as_domain\" rather than repeating them.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "array",
"items": {
"type": "string"
}
}
},
"records_source": {
"type": [
"string",
"null"
],
"description": "Resolver IP whose answers populated \"records\", or null when no resolver was queried."
},
"resolver_results": {
"type": "array",
"items": {
"type": "object",
"required": [
"resolver",
"latency_ms",
"records",
"records_same_as_domain",
"status",
"status_by_type",
"error"
],
"properties": {
"error": {
"type": [
"string",
"null"
],
"description": "Failure summary for this resolver in the form \"SERVFAIL on A, MX\", or null when every requested type either resolved or returned nodata. Nodata is never reported as an error — it is a valid DNS answer."
},
"status": {
"enum": [
"ok",
"nodata",
"nxdomain",
"servfail",
"refused",
"timeout",
"error"
],
"type": "string",
"description": "Headline outcome for this resolver: \"ok\" when any requested record type resolved, otherwise the most actionable failure across the requested types (servfail, timeout, refused, error, nxdomain, nodata — in that order). Read \"status_by_type\" for the per-record-type detail."
},
"records": {
"type": "object",
"description": "Records returned by this resolver, keyed by type — carrying only the types whose values differ from the domain-level \"records\" set. A type this resolver answered identically is named in \"records_same_as_domain\" instead of repeated here. A requested type in neither place returned nothing from this resolver; \"status_by_type\" says why.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "array",
"items": {
"type": "string"
}
}
},
"resolver": {
"type": "string",
"description": "Resolver IP address used."
},
"latency_ms": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Round-trip resolution latency in milliseconds."
},
"status_by_type": {
"type": "object",
"description": "Outcome for each requested record type, keyed by type. \"ok\" = records returned; \"nodata\" = the domain exists but has no record of this type; \"nxdomain\" = the domain does not exist (check for a typo, an expired registration, or a missing delegation); \"servfail\" = the resolver could not complete the query, commonly a DNSSEC validation failure; \"refused\" = the resolver declined the query or refused the connection; \"timeout\" = no answer within timeout_ms; \"error\" = any other failure, described in \"error\".",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"enum": [
"ok",
"nodata",
"nxdomain",
"servfail",
"refused",
"timeout",
"error"
],
"type": "string"
}
},
"records_same_as_domain": {
"type": "array",
"items": {
"type": "string",
"description": "A record type answered exactly as the domain-level set."
},
"description": "Record types this resolver answered with exactly the domain-level \"records\" values, omitted from \"records\" above rather than duplicated. Read their values from the domain-level set. Resolvers agreeing is the common case, so this list is usually where most of the answer is."
}
},
"description": "DNS resolution result from one resolver.",
"additionalProperties": false
},
"description": "Per-resolver breakdown for propagation analysis."
},
"propagation_discrepancies": {
"type": "array",
"items": {
"type": "object",
"required": [
"record_type",
"resolvers_agree",
"kind",
"values_by_resolver",
"status_by_resolver"
],
"properties": {
"kind": {
"enum": [
"value_variation",
"partial_resolution"
],
"type": "string",
"description": "What the disagreement is. \"partial_resolution\" = at least one resolver returned records and at least one returned nothing; this is the signal worth investigating (in-flight propagation, a broken resolver, or a partial delegation) — read \"status_by_resolver\" for why each empty resolver was empty. \"value_variation\" = every resolver answered but with different values; this is the expected steady state for anycast and geo-steered domains such as CDN-fronted hostnames, and is also consistent with an in-flight DNS change. Neither value asserts a cause on its own."
},
"record_type": {
"type": "string",
"description": "The DNS record type resolvers disagreed on."
},
"resolvers_agree": {
"type": "boolean",
"description": "Always false — an entry only exists when resolvers disagreed."
},
"status_by_resolver": {
"type": "object",
"description": "Outcome for this record type per resolver IP address — explains an empty entry in \"values_by_resolver\" as nodata, nxdomain, servfail, timeout, refused, or error.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"enum": [
"ok",
"nodata",
"nxdomain",
"servfail",
"refused",
"timeout",
"error"
],
"type": "string"
}
},
"values_by_resolver": {
"type": "object",
"description": "Values reported per resolver IP address. An empty array means that resolver returned no records of this type.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "array",
"items": {
"type": "string"
}
}
}
},
"description": "A record type where resolvers returned different answers.",
"additionalProperties": false
},
"description": "Record types where resolvers returned different answers, each labelled by \"kind\". Empty when all resolvers agree."
}
},
"description": "DNS resolution result for one domain.",
"additionalProperties": false
},
"description": "Per-domain DNS resolution results."
},
"deferred_domains": {
"type": "array",
"items": {
"type": "string",
"description": "A submitted domain entry, exactly as sent."
},
"description": "Domain entries past the first 10, not queried on this call, verbatim and in input order. Resend them in another call. Empty when every entry was queried."
},
"deferred_resolvers": {
"type": "array",
"items": {
"type": "string",
"description": "A submitted resolver entry, exactly as sent."
},
"description": "Distinct resolvers past the first 5, not queried on this call, verbatim and in input order. Resend them with the same domains in another call. Empty when every resolver was queried."
}
},
"additionalProperties": false
}devops_check_dns annotations
{
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}devops_suggest_action — Devops Suggest Action
Advertised read-only
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.
devops_suggest_action input schema
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"vendor"
],
"properties": {
"vendor": {
"type": "string",
"minLength": 1,
"description": "Vendor slug, display name, or raw status page URL (e.g., \"cloudflare\", \"Amazon Web Services\"). Used to tailor category-specific guidance (CDN outage vs. CI/CD outage vs. auth provider outage). A name that matches no registry vendor gets a devops_list_vendors search as its first follow-up instead of an incidents call."
},
"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). Values pre-filled by devops_status_check read \"Group / Leaf\" for a component the status page files under a group. Used to tailor suggestions to the impacted subsystem."
}
},
"additionalProperties": false
}devops_suggest_action output schema
{
"type": "object",
"anyOf": [
{
"not": {
"required": [
"error"
]
},
"required": [
"vendor",
"vendor_category",
"guidance",
"diagnostics_summary",
"nextToolSuggestions"
]
},
{
"required": [
"error"
]
}
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "JSON-RPC error code for this failure."
},
"data": {
"type": "object",
"properties": {
"reason": {
"type": "string",
"description": "Machine-readable failure mode."
},
"recovery": {
"type": "object",
"required": [
"hint"
],
"properties": {
"hint": {
"type": "string"
}
},
"description": "Actionable next step for the caller.",
"additionalProperties": {}
},
"retryable": {
"type": "boolean",
"description": "Whether retrying may succeed."
}
},
"additionalProperties": {}
},
"message": {
"type": "string",
"description": "Human-readable description of what went wrong."
}
},
"description": "Present when the call failed. Absent on success.",
"additionalProperties": {}
},
"vendor": {
"type": "string",
"description": "Vendor as provided."
},
"guidance": {
"type": "string",
"description": "Markdown playbook — immediate steps, diagnostic checks, mitigation options, and what to monitor for resolution. Tailored to the vendor category, reported severity, and affected components."
},
"vendor_category": {
"type": [
"string",
"null"
],
"description": "Detected category from registry (e.g., \"cdn-edge\", \"auth\"). Null for unrecognized vendors."
},
"diagnostics_summary": {
"type": "object",
"required": [
"vendor_indicator",
"affected_components",
"incident_snippet"
],
"properties": {
"incident_snippet": {
"type": [
"string",
"null"
],
"description": "The incident_summary input echoed in full for context, or null when not provided."
},
"vendor_indicator": {
"anyOf": [
{
"enum": [
"none",
"minor",
"major",
"critical",
"maintenance"
],
"type": "string"
},
{
"type": "null"
}
],
"description": "Vendor status indicator echoed from the vendor_indicator input, or null when not provided."
},
"affected_components": {
"type": "array",
"items": {
"type": "string"
},
"description": "Affected component names echoed from the affected_components input."
}
},
"description": "Summary of input context used to generate the playbook.",
"additionalProperties": false
},
"nextToolSuggestions": {
"type": "array",
"items": {
"type": "object",
"required": [
"toolName",
"reason",
"args"
],
"properties": {
"args": {
"type": "object",
"description": "Ready-to-use arguments for the suggested tool call.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"reason": {
"type": "string",
"description": "Why this step is recommended given the incident context."
},
"toolName": {
"type": "string",
"description": "Tool to call next (e.g., \"devops_get_incidents\", \"devops_list_vendors\", \"devops_check_dns\")."
}
},
"description": "A recommended follow-up tool call with pre-filled arguments.",
"additionalProperties": false
},
"description": "Recommended follow-up calls with arguments already populated. Execute these in sequence to gather diagnostic data."
}
},
"additionalProperties": false
}devops_suggest_action annotations
{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true
}Prompts
0 advertised
Resources
1 advertised
devops-status-guide
Gates and identifier chains for the devops_* tools. Covers what a vendor status reading can and cannot establish, how far incident history reaches on each backend, where regions live, and how to check a DNS change against the zone's own nameservers and a certificate failure against CAA. Use before calling a vendor up, down, or incident-free on a date, when scoping an outage to a region, in pre-deploy sweeps and postmortems, and when diagnosing a domain's DNS or TLS.
devops-status-guide URI
skill://devops-status-guide/SKILL.mddevops-status-vendor — devops-status-vendor
Full registry entry for a vendor by slug — status page URL, category, and API type. Read-only, stable. Use devops_list_vendors to discover available slugs.
devops-status-vendor URI template
devops-status://vendors/{name}io.modelcontextprotocol/skills
io.modelcontextprotocol/skills URI template
skill://{+path}90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-07: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 715 ms
- 95th percentile latency
- 715 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 715 ms · metadata changed · 7 tool(s), 1 resource(s), 2 resource template(s), 0 prompt(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
Claude Code configuration
claude mcp add --transport http devops-status-mcp-server-caseyjhand https://devops-status.caseyjhand.com/mcpCodex
Codex configuration
codex mcp add devops-status-mcp-server-caseyjhand --url https://devops-status.caseyjhand.com/mcpCursor
Cursor configuration
{
"mcpServers": {
"devops-status-mcp-server-caseyjhand": {
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}Cline
Cline configuration
{
"mcpServers": {
"devops-status-mcp-server-caseyjhand": {
"type": "streamableHttp",
"url": "https://devops-status.caseyjhand.com/mcp",
"disabled": false
}
}
}VS Code
VS Code configuration
{
"servers": {
"devops-status-mcp-server-caseyjhand": {
"type": "http",
"url": "https://devops-status.caseyjhand.com/mcp"
}
}
}Gemini CLI
Gemini CLI configuration
gemini mcp add --transport http devops-status-mcp-server-caseyjhand https://devops-status.caseyjhand.com/mcpClaude Desktop
Claude Desktop configuration
https://devops-status.caseyjhand.com/mcpWindsurf
Windsurf configuration
{
"mcpServers": {
"devops-status-mcp-server-caseyjhand": {
"serverUrl": "https://devops-status.caseyjhand.com/mcp"
}
}
}Let your agent find its tools
Find servers like devops-status-mcp-server from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.