Categories › Web & Browser › SEO & site audits
DNS comparison, Claude and cloud components/incidents, and website diagnostics. Free; no API key.
Remote server: your requests and data go to webupcheck.com. Claude Code: claude mcp add --transport http webupcheck-dns-website-provider-diagnost https://webupcheck.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
check_website — Use when a public website will not load or you need a fresh server-side availability observation. Returns HTTP status, DNS answers, redirectget_service_status — Read the latest scheduled homepage observation and up to 12 recent samples for a curated service. Includes freshness, scope and the officiallist_monitored_services — Discover curated service IDs, homepage URLs, measurement scopes and official status dashboards. No new website probe. Use get_service_statusget_provider_incidents — Use for official active incident reports from Claude, OpenAI, Google Cloud, Google Workspace, Google Search, Cloudflare, GitHub or Wikimediainvestigate_incident — Use when a public endpoint fails and you need evidence-based next steps. Combines one protected HTTP/DNS check, existing homepage history whget_provider_components — Use to distinguish Claude API/Claude Code, OpenAI Responses/Chat Completions and other listed components from a working homepage. Supported:check_dns — Use for public-domain DNS diagnosis: compare A/AAAA/CNAME/NS/MX/TXT/CAA records, TTL, DNS response codes and resolver-reported DNSSEC AD. OnNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.