Skip to content
Ned Watch logo

Ned Watch MCP server

Which MCP servers are Ned Watch'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-26

← Back to Ned Watch

Whose server it is
  • Registry namewatch.ned/ned-watchverified in the MCP registry

The registry name sits under ned.watch. 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-26
  • Stateanswerschecked 2026-10-26
  • Tools12
  • Server calls itselfNed Watch
  • Server version1.30.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • watch_cancel change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 10 of 12 tools: check arguments before calling.

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: 1, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer163 ms
  • Space in an agent's context≈ 1,984 tokensthe definitions of all its tools (12), which an agent carries on every turn
  • Tool definitionsC · 69 of 100
  • Typed results0 of 12 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 10 of 12
  • Not saying whether it only reads or can destroy: 12 of 12

Worth a look

  • Tools that change data, on a server that answers without a sign-in: watch_cancel

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 offers12 tools · read 2026-10-26
  • is_up

    Ask before you call. No key needed. Returns the state of everything Ned watches publicly on a host (and its subdomains) from two continents: up, degraded (answered, but their own status page reports an incident), down, reachable (answers…

  • watch_register

    Register a watch. type: deadman | http | tls (for overrun and content use overrun_watch / content_watch). notify: up to 3 Discord/Slack/Teams webhook URLs told on fire, clear and change, so a human hears even if the agent behind…

  • quickstart

    The fastest way to be watched, in one call. Makes you an agent (if you have no key yet) and a deadman watch that expects a check-in every `every_minutes` (5 to 1440). Miss one and Ned POSTs a signed message to callback_url; check in again…

  • watch_get

    Current state of one of your watches: status, fired, fire_count, next_check, last_state.

  • watch_cancel

    Cancel a watch you registered. Frees a free-tier slot.

  • deadman_checkin

    Check in on a deadman watch to keep it from firing. Proves you hold the watch's signing_secret (returned at registration): it is sent as Authorization: Bearer <signing_secret> for this one call. No agent key needed.

  • overrun_watch

    Fire when something is STILL running past its deadline (the other side of a deadman). Register once, then call overrun_start when a run begins and overrun_finish when it ends. If a run isn't finished within max_runtime_s (60 to 86400)…

  • overrun_start

    A run began on an overrun watch. Returns run_id and deadline. Sends the watch's signing_secret as Authorization: Bearer for this one call; no agent key needed. run_id is optional (your own id, 1-64 chars); pass one and a retried start is…

  • overrun_finish

    The run ended. Returns runtime_s and late. If Ned already fired for this run, your callback gets 'clear' with late: true. Finishing with no run open is an error (409). failed=true says the run crashed: Ned fires at once with your short…

  • content_watch

    Fire when a URL answers but says the wrong thing. expect has 1 to 5 conditions: status (int), contains / not_contains (a string or list of strings), json_path (dotted, e.g. "data.items.0.state") with equals (a JSON scalar) or exists…

  • balance

    Your balance in cents, free allowance used, burn per day, days left, and the top-up routes.

  • pricing

    Ned Watch pricing: 5 free watches at >=300s, then per-day rates (http/tls/content 2c, fast 7c, deadman 1c, overrun 1c) from a prepaid balance topped up over x402 (USDC on Base). Public, no key needed. Paying is done against POST…

How to connect

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

{
  "mcpServers": {
    "ned-watch": {
      "type": "http",
      "url": "https://api.ned.watch/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http ned https://api.ned.watch/mcp

Add to CursorAdd to VS Code

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

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.