Devops Status Mcp Server

io.github.cyanheads由 GitHub 账号 cyanheads 发布v0.11.2更新于 Nov 16, 2026

供应商状态页面、TLS 证书检查、DNS 传播检查以及事件响应手册。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

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

发布方自己的服务:status.live national parks

已验证Streamable HTTP可网页运行云端与基础设施安全与监控

概览

Devops Status 的托管 MCP 服务(devops-status.caseyjhand.com);无需登录;Streamable HTTP;7 个工具。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

端点
devops-status.caseyjhand.com
最近检查

安装

在 SourceWeft 中

  1. 打开 控制台中的 Devops Status Mcp Server,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.cyanheads%2Fdevops-status-mcp-server/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "devops-status": {
      "type": "http",
      "url": "https://devops-status.caseyjhand.com/mcp"
    }
  }
}

README

@cyanheads/devops-status-mcp-server

Check vendor status pages, inspect SSL/TLS certificates, verify DNS propagation, and get incident-response playbooks via MCP. STDIO or Streamable HTTP.

7 Tools • 1 Resource


Overview

Status pages for 71 vendors — AWS, Google Cloud, Azure, Slack, and more — in one normalized format. Check who's down, pull incident timelines, watch your stack, and get an incident-response playbook. Plus TLS certificate and DNS checks for any domain. No API keys required.

Tools

ToolDescription
devops_list_vendorsList vendors in the built-in registry, optionally filtered by name or category. Returns slug, display name, category, and status page URL.
devops_status_checkCheck the current health status for one or more vendors. Returns per-vendor indicator (none / minor / major / critical / maintenance), degraded components, and active incident summaries.
devops_get_incidentsFetch incident history for a vendor — active, resolved, or scheduled maintenance. Returns the full incident timeline with per-update bodies and affected components.
devops_watch_stackCheck the health of a named vendor stack. Where the server identifies the caller (stdio, or HTTP with jwt/oauth auth), pass vendors once to save the list and later calls reuse it; on HTTP with MCP_AUTH_MODE=none nothing is saved and vendors is required on every call. Returns an aggregate health rollup plus per-vendor detail.
devops_check_certsInspect SSL/TLS certificate health for one or more domains via a real TLS handshake. Reports expiry, chain depth, protocol version, cipher suite, and HSTS presence on HTTP ports. Pure TypeScript — no external API.
devops_check_dnsResolve DNS records and verify propagation for one or more domains across Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9). Reports per-resolver latency and resolver discrepancies. Pure TypeScript — no external API.
devops_suggest_actionInstruction tool — returns a tailored incident-response playbook and pre-filled follow-up tool calls given a vendor name and optional incident context. No external calls; fully deterministic.

Resources

ResourceDescription
devops-status://vendors/{name}Full registry entry for a vendor by slug — status page URL, category, and API type.

All resource data is also reachable via tools. Tool-only agents are fully supported.


Capability reference

devops_list_vendors tool

  • Optional free-text query (name and slug, case-insensitive) and optional category: cloud, cdn-edge, dev-platform, data, comms, auth, monitoring, ai
  • Returns slug (what to pass to other tools), display name, category, and status page URL; an empty result carries a notice naming what missed
  • 71 built-in entries, most on Atlassian Statuspage; fly-io, planetscale, supabase, brevo, clerk, openai, elevenlabs, and cohere (incident.io-hosted pages, read through their own page feed); aws, gcp, azure, azure-devops, gitlab, neon, slack, redis-cloud, and the nine Datadog site entries (datadog for US1, datadog-us3, datadog-us5, datadog-eu1, datadog-uk1, datadog-ap1, datadog-ap2, datadog-us1-fed, datadog-us2-fed) use native-API adapters. Statuspage-compatible pages not in the registry work by passing a raw base URL to other tools
  • These Atlassian products have their own entry (jira, confluence, bitbucket, jira-service-management, atlassian-compass, atlassian-developer, trello, opsgenie, atlassian-statuspage, atlassian-guard). atlassian reads the umbrella page, which publishes no components and only cross-product incidents; any tool serving it says so in notice and names those slugs

Built-in vendor registry:

CategoryVendors
clouddigitalocean, linode, aws, gcp, azure
cdn-edgecloudflare, akamai
dev-platformgitlab, github, azure-devops, npm, vercel, netlify, render, fly-io, circleci, travis-ci, snyk, atlassian, jira, confluence, bitbucket, jira-service-management, atlassian-compass, atlassian-developer, trello, figma, launchdarkly
datamongodb-atlas, planetscale, supabase, neon, redis-cloud, elastic, influxdb, upstash, cloudinary, segment
commsslack, discord, twilio, sendgrid, mailgun, hubspot, brevo, courier, loops
authauth0, clerk, workos, atlassian-guard
monitoringdatadog, datadog-us3, datadog-us5, datadog-eu1, datadog-uk1, datadog-ap1, datadog-ap2, datadog-us1-fed, datadog-us2-fed, sentry, new-relic, grafana-cloud, honeycomb, opsgenie, atlassian-statuspage
aiopenai, anthropic, elevenlabs, pinecone, cohere

devops_status_check tool

  • Accepts vendor slugs (e.g., github, aws) or raw Atlassian Statuspage base URLs, mixed freely; a URL is read at its origin and path. A URL on the status page of a vendor read through another backend (https://status.gitlab.com) gets an error naming its slug, and a URL on an incident.io page reads that page's Statuspage-compatible API, which lists 25 components and 25 incidents at most, with no component groups and maintenance windows without their times — pass the slug (openai) for the full feed. Up to 20 are checked per call; the rest come back in deferred_vendors with a notice to resend them. More than 100 entries is rejected (invalid_arguments)
  • mode: "summary" (default) returns the indicator, degraded components, and active incidents; mode: "detailed" adds the full component list (component_limit, default 50, clamped to 500) and scheduled maintenance windows. component_filter matches component or group names
  • A list longer than component_limit pages: each capped vendor returns next_component_offset, which you pass back as component_offset (applied after component_filter). degraded_components and active_incidents are complete on every page
  • One failing vendor never blocks the rest (per-vendor error field). Results are cached for 60 seconds (cached: true), and summary counts operational / degraded / down / maintenance / unavailable
  • indicator is the vendor's own rating, and a Statuspage page can keep it at none while an incident it rated minor or worse is open. summary counts each vendor at the worse of the two; incidents rated none or maintenance and scheduled windows never count as an outage
  • nextToolSuggestions pre-fills a devops_suggest_action call for each vendor with an active problem — the vendors counted degraded or down

devops_get_incidents tool

  • filter: all (default), active, resolved, or scheduled (maintenance windows only). limit (default 20, max 50) with offset for paging
  • Returns per-update bodies as plain text in chronological order, affected component names, duration in minutes for resolved incidents, and a shortlink. Google Cloud and AWS incidents also carry affected_locations (region ID, name, and whether it is still affected; on AWS, the one region the event names, or global). Each incident carries source: api, or history for an archive record (title, impact, times, and final message only)
  • since and until (YYYY-MM-DD, UTC) bound the start date and work with filter: "all" or "resolved"; since also reads the Statuspage history archive back up to 24 months, past the API's newest-50 limit; a call that hits that limit without since is told to set it. On incident.io vendors the feed lists the last 90 days, a notice says when the page publishes older incidents, and since reads them back up to 24 months as full records. match keeps incidents whose title, component names, or (on Google Cloud and AWS) location names and IDs contain every space-separated term given (up to 200 characters); a term joined by punctuation, such as eu-central-1, must find its words together and in order within one of them
  • Responses are capped at 64,000 bytes per surface; a cut page sets truncated: true and nextOffset. full_updates: true keeps every update on a single oversized incident
  • Errors: invalid_since and invalid_until (filter: "active" or "scheduled", or until before since); statuspage_not_found (a raw URL that serves no Atlassian Statuspage API, naming the registry slug where one exists; not retryable, unlike statuspage_unavailable)
  • Feeds with no data for a filter return empty: resolved for Azure, scheduled for AWS, Azure, Azure DevOps, Google Cloud, and Slack, and for a Statuspage page that publishes no maintenance feed (a notice says so). An empty active or resolved that read no incident suggests scheduled only where the vendor publishes maintenance windows. History is short where a vendor reads no archive: AWS keeps resolved events for a few hours, and Status.io (gitlab, neon) lists current incidents only. On those feeds a since earlier than the oldest record returned, or an until without since, gets a notice naming the date the feed starts

devops_watch_stack tool

  • Pass vendors (up to 20) once to save the stack under stack_name (1-64 characters; several stacks can coexist, e.g. "production"); later calls can omit vendors. Over 20 is rejected with stack_too_large. Saving works on stdio and on HTTP with MCP_AUTH_MODE=jwt|oauth; with the default in-memory storage, saved stacks do not survive a restart
  • On HTTP with MCP_AUTH_MODE=none nothing is saved: a call with vendors runs the sweep and returns stack_persisted: false, and a call without vendors fails with vendors_required
  • Aggregate health: all_operational / maintenance / degraded / partial_outage / major_outage / unknown (a vendor could not be reached), rolled up from the same per-vendor rating as summary. component_limit and nextToolSuggestions work as in devops_status_check; there is no component_offset, so a capped vendor's next_component_offset continues in devops_status_check

devops_check_certs tool

  • Accepts hostnames, IP addresses, host:port, or URLs; a port on the entry overrides port (default 443). The first 10 entries are inspected (up to 100 accepted); the rest come back in deferred_domains to resend
  • Reports days to expiry (warning under 30 days, critical under 7), subject and SANs, issuer, chain depth, TLS version (1.0 and 1.1 flagged insecure), cipher suite, and HSTS on HTTP ports
  • status: "critical" separates a hostname mismatch (hostname_verification_error) from an untrusted chain (authorization_error). Per-domain failures come back inline as status: "error" with the reason in error
  • timeout_ms is one deadline per domain (max 15000)

devops_check_dns tool

  • Accepts domain names, URLs, or host:port; the first 10 domains are queried (up to 100 accepted) and the rest come back in deferred_domains. IP addresses get their own error row
  • Queries Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9) in parallel for A, AAAA, CNAME, MX, TXT, NS, CAA, and SOA (default A, AAAA, MX, TXT)
  • Reports per-resolver latency and typed discrepancies: partial_resolution (some resolvers did not answer) is a real problem; value_variation (different values) is normal for anycast or geo-steered domains
  • Custom resolvers take public IP literals, first 5 queried and the rest in deferred_resolvers; private and loopback addresses need DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS=true. timeout_ms applies per domain and resolver (max 10000)

devops_suggest_action tool

  • Takes a vendor slug or display name and returns a category-tailored markdown playbook, with generic guidance for unrecognized vendors
  • Optional incident_summary, affected_components, and vendor_indicator add a subsystem section and severity-based urgency
  • nextToolSuggestions pre-fills follow-up calls, including cert and DNS checks when your_domain is given. With DEVOPS_STATUS_DISABLE_ACTIVE_PROBES=true, guidance uses manual commands (dig, openssl s_client) instead

devops-status://vendors/{name} resource

  • Returns the full registry entry for a vendor slug: status page URL, category, API type (statuspage, statusio, slack, aws, gcp, azure, azure-devops, firehydrant, datadog, incidentio), component_scope_prefix where a vendor covers part of a shared page (sendgrid), and product_slugs on an umbrella page that publishes no components (atlassian)
  • Cached publicly for 1 hour; the same data is reachable via devops_list_vendors

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

DevOps-status-specific:

  • No API keys required — every status backend is a public API; TLS and DNS use the Node.js standard library
  • 71-vendor built-in registry across eight categories; native adapters normalize incident.io, Status.io, Slack, AWS Health, Google Cloud, Azure, Azure DevOps, Firehydrant, and Datadog into the Statuspage shape
  • Vendor-authored text is escaped so it reads as data, not markup; DNS record values and certificate names render as code spans that read back exactly as resolved
  • 60-second in-memory cache on status reads, shared across tenants; concurrent reads of one URL share a single request
  • devops_watch_stack saves named vendor lists for repeat checks and pre-deploy sweeps
  • devops_suggest_action is deterministic, with no LLM sampling dependency

Agent skill:

  • devops-status-guide carries the gates for using these tools together: what a status reading can and cannot establish, how far incident history reaches on each backend, where regions live, and how to diagnose a DNS change or a certificate failure. MCP clients read it from the server as skill://devops-status-guide/SKILL.md; it also ships in the npm package, the Docker image, and the .mcpb bundle, and plugin installs scan it from skills/.

Agent-friendly output:

  • Batch tools never let one failing target block the rest; errors come back as inline error fields
  • checked_at on every status result is the time of the check; cached: true marks a status read served from the cache, which can be up to the cache TTL (60 seconds by default) older
  • Fixed indicator and status enums (none / minor / major / critical / maintenance) let callers branch on data
  • nextToolSuggestions pre-fills follow-up tool arguments from incident context

Getting started

Connect to the hosted instance, no install:

sh
claude mcp add --transport http devops-status-mcp-server https://devops-status.caseyjhand.com/mcp

Or run it locally:

sh
claude mcp add devops-status-mcp-server -- npx -y @cyanheads/devops-status-mcp-server

For other clients, add this to the MCP config file:

json
{  "mcpServers": {    "devops-status-mcp-server": {      "command": "npx",      "args": ["-y", "@cyanheads/devops-status-mcp-server"]    }  }}

No API key required. For Docker or a source build, see Running the server.


Configuration

No API keys required. All environment variables are optional.

VariableDescriptionDefault
DEVOPS_STATUS_CACHE_TTL_MSIn-memory cache TTL for vendor status reads (all backends) in milliseconds.60000
DEVOPS_STATUS_FETCH_TIMEOUT_MSPer-request timeout for vendor status API calls (all backends) in milliseconds; a since history read also holds its pages to what is left of its 30-second limit.8000
DEVOPS_STATUS_CERT_TIMEOUT_MSDefault timeout_ms for devops_check_certs (1000–15000).5000
DEVOPS_STATUS_DNS_TIMEOUT_MSDefault timeout_ms for devops_check_dns (1000–10000).3000
DEVOPS_STATUS_ALLOW_PRIVATE_TARGETSWhen true, disables the SSRF guards on user-supplied status-page URLs, devops_check_certs hosts, and devops_check_dns resolver IPs. Trusted local deployments only.false
DEVOPS_STATUS_DISABLE_ACTIVE_PROBESWhen true, removes devops_check_dns and devops_check_certs. For shared public instances.false
MCP_TRANSPORT_TYPETransport: stdio or http.stdio
MCP_HTTP_PORTPort for HTTP server.3010
MCP_SESSION_MODEHTTP session handling: stateless, stateful, or auto.stateless
MCP_AUTH_MODEAuth mode: none, jwt, or oauth.none
MCP_LOG_LEVELLog level (RFC 5424).info
LOGS_DIRDirectory for log files (Node.js only).<project-root>/logs
OTEL_ENABLEDEnable OpenTelemetry instrumentation.false

An invalid DEVOPS_STATUS_* value stops startup with an error naming the variable.

See .env.example for the full list of optional overrides.


Running the server

Local development

Requires Bun v1.4.4 or higher (or Node.js v24+).

  • Clone and install:

    sh
    git clone https://github.com/cyanheads/devops-status-mcp-server.gitcd devops-status-mcp-server && bun installcp .env.example .env   # optional overrides
  • Build and run:

    sh
    bun run rebuildbun run start:stdio# orbun run start:http
  • Run checks and tests:

    sh
    bun run devcheck   # Lint, format, typecheck, securitybun run test       # Vitest test suitebun run lint:mcp   # Validate MCP definitions against spec

Docker

sh
docker run --rm -p 3010:3010 ghcr.io/cyanheads/devops-status-mcp-server:latest

The image defaults to HTTP transport, stateless session mode, and logs to /var/log/devops-status-mcp-server. To run it over stdio from an MCP client, use "command": "docker" with "args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT_TYPE=stdio", "ghcr.io/cyanheads/devops-status-mcp-server:latest"]. To build locally, docker build -t devops-status-mcp-server .; OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.


Project structure

PathPurpose
src/index.tscreateApp() entry point — registers tools, resources, and inits services.
src/config/Server-specific environment variable parsing and validation with Zod.
src/mcp-server/tools/Tool definitions (*.tool.ts).
src/mcp-server/resources/Resource definitions (*.resource.ts).
src/services/cert/node:tls — TLS handshake, X.509 parsing, expiry and protocol flagging, legacy-TLS retry, HSTS read.
src/services/dns/DNS wire client (node:dgram / node:net): message encoding and bounds-checked decoding, UDP with TCP retry; multi-resolver fan-out and propagation discrepancy detection.
src/services/statuspage/Statuspage public API client (reads through the shared cache in src/utils/cached-fetch.ts).
src/services/status-adapters/Native-API adapters (incident.io, Status.io, Slack, AWS Health, Google Cloud Service Health, Azure status, Azure DevOps status, Firehydrant, Datadog), the shared RSS extractor, + api_type dispatch, normalizing into the Statuspage shapes.
src/services/vendor-registry/In-memory vendor registry loaded from src/data/vendor-registry.ts.
src/data/Static vendor registry data file (vendor-registry.ts).
src/utils/Shared helpers — response cache and fetch, SSRF guard, domain-entry normalizer, HTML-to-text, vendor-text markdown escaping, code-span rendering of DNS and certificate values, input-bound notices, word matching.
skills/Published agent skill (devops-status-guide), served over MCP and shipped in the npm package, Docker image, and .mcpb bundle.
tests/Vitest tests mirroring src/.

Development guide

See CLAUDE.md for development guidelines and architectural rules. The short version:

  • Handlers throw, framework catches — no try/catch in tool logic
  • Use ctx.log for request-scoped logging, ctx.state for tenant-scoped storage
  • Register new tools and resources via the barrels in src/mcp-server/*/definitions/index.ts
  • devops_check_certs and devops_check_dns use only Node.js stdlib — add no external deps for these paths

Contributing

Issues are welcome. Run checks and tests before submitting:

sh
bun run devcheckbun run test

License

Apache-2.0 — see LICENSE for details.

来源:README.md,提交 5a23919

工具

7

devops_list_vendors

Devops List Vendors

List vendors in the built-in registry, optionally filtered by category or name search. Returns slug, display name, category, and status page URL for each entry. Use to discover the correct slug to pass to other tools, or to see which vendors are available before configuring a stack.

输入参数querycategory

devops_status_check

Devops Status Check

Check the current health status for one or more vendors. Accepts registered vendor slugs (e.g., "github", "aws", "gcp", "gitlab") or raw Atlassian Statuspage base URLs. Registry entries are served by each vendor's native status API (Statuspage, incident.io, 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.

输入参数modevendors必填component_limitcomponent_filtercomponent_offset

devops_get_incidents

Devops Get Incidents

Fetch incident history and scheduled maintenance windows for a vendor. Returns full incident timeline — each investigator update, affected components, and resolution. Filter by status to focus on active incidents (use before deploy), resolved history (for postmortem), or maintenance windows: upcoming and in-progress ones, plus completed ones on Atlassian Statuspage, incident.io, 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. On incident.io vendors (such as "openai"), whose feed lists the last 90 days by default, since reads the page's incident list one calendar quarter at a time back to that date, 24 months back at most, and returns full records (source: "api"). An empty result, or a history

输入参数limitmatchsinceuntilfilteroffsetvendor必填full_updates

devops_watch_stack

Devops Watch Stack

Check the health of a named vendor stack — a saved list of vendors representing your infrastructure dependencies. On the first call, provide vendors to define the stack; subsequent calls can omit vendors to reuse the saved list. Stacks are saved per authenticated caller, or per local server process; 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").

输入参数modevendorsstack_namecomponent_limitcomponent_filter

devops_check_certs

Devops Check Certs

Inspect SSL/TLS certificate health for one or more domains by performing a real TLS handshake. Works for any internet-accessible domain — no vendor registry required. Reports days to expiry (flagged at < 30 days warning and < 7 days critical), certificate subject and SANs, issuer, hostname coverage, 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.

输入参数portdomains必填timeout_ms

devops_check_dns

Devops Check Dns

Resolve DNS records for one or more domains across multiple public resolvers and compare what each resolver returned. Works for any domain — no vendor registry required. Reports records found (A/AAAA/CNAME/MX/TXT/NS/CAA/SOA), resolution latency per resolver, and a typed outcome per resolver and 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.

输入参数domains必填resolverstimeout_msrecord_types

devops_suggest_action

Devops Suggest Action

Return an incident-response playbook tailored to a vendor degradation, with pre-filled follow-up tool calls. Synthesizes category-specific guidance (cloud, CDN, dev-platform, auth, etc.) from built-in incident knowledge and the provided context. Use after devops_status_check or devops_get_incidents surfaces a problem to determine what to investigate next.

输入参数vendor必填your_domainincident_summaryvendor_indicatoraffected_components

版本历史

9
  1. v0.11.2最新Nov 16, 2026
  2. v0.11.1Nov 1, 2026
  3. v0.11.0Oct 31, 2026
  4. v0.10.0Oct 15, 2026
  5. v0.9.1Oct 8, 2026
  6. v0.9.0Sep 25, 2026
  7. v0.8.3Sep 25, 2026
  8. v0.8.2Sep 20, 2026
  9. v0.8.1Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Status 集成