Skip to content
WebUpCheck logo

WebUpCheck MCP server

Which MCP servers are WebUpCheck's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to WebUpCheck

Whose server it is
  • Registry namecom.webupcheck/webupcheckverified in the MCP registry

The registry name sits under webupcheck.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools7
  • Server calls itselfwebupcheck
  • Server version1.5.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 53 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: limit request bursts from individual callers; block repeated failed login attempts automatically; restrict scanners probing for missing pages.
  • Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it0 of 3 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer90 ms
  • Space in an agent's context≈ 1,603 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results7 of 7 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • cannot · limit request bursts from individual callers
  • cannot · block repeated failed login attempts automatically
  • cannot · restrict scanners probing for missing pages

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-28
  • check_website

    Use when a public website will not load or you need a fresh server-side availability observation. Returns HTTP status, DNS answers, redirect chain, HTTPS connection evidence, timestamps and bounded retry attempts. Blocked or inconclusive…

  • get_service_status

    Read the latest scheduled homepage observation and up to 12 recent samples for a curated service. Includes freshness, scope and the official status link. Does not make a new request to the target website. Scheduled about every 15 minutes…

  • list_monitored_services

    Discover curated service IDs, homepage URLs, measurement scopes and official status dashboards. No new website probe. Use get_service_status for existing observations or check_website for any public hostname.

  • get_provider_incidents

    Use for official active incident reports from Claude, OpenAI, Google Cloud, Google Workspace, Google Search, Cloudflare, GitHub or Wikimedia. Returns affected components where reported, source links, updates, retrieval timestamps and…

  • investigate_incident

    Use when a public endpoint fails and you need evidence-based next steps. Combines one protected HTTP/DNS check, existing homepage history where supported, and optional official provider incidents. Provider is inferred only for known…

  • get_provider_components

    Use to distinguish Claude API/Claude Code, OpenAI Responses/Chat Completions and other listed components from a working homepage. Supported: Claude, OpenAI, Cloudflare, GitHub, Wikimedia. Optional component accepts an exact ID or…

  • 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. One record type per call (default A), compared across two public recursive resolvers. Distinguishes…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "webupcheck": {
      "type": "http",
      "url": "https://webupcheck.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http webupcheck https://webupcheck.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://webupcheck.com/mcp as a custom connector in the settings.

Other servers listed as WebUpCheck's
  • com.webupcheck/protectanswers, requires sign-inverified in the MCP registry

OpenAPI spec

7 paths, read 2026-10-28. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.