Ned Watch MCP Server

by ned Your server? Claim it

not responding

Ned Watch is listed as active in the registry but did not answer our last check. It exposes 12 tools.

Wake me when my agent misses its heartbeat. Deadman, overrun, HTTP, TLS, content; US+EU nodes.

Uptime history 40 days of history · worst day 22%

40 days agonow

27.5%

Uptime 24h

25 of 91 checks

Tools

read from the server

295 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 14

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

7 Oct a tool appeared is_up

7 Oct a tool description was rewritten watch_register

7 Oct a tool changed the parameters it asks for watch_register

5 Oct 2 tool descriptions were rewritten overrun_finish, quickstart

5 Oct 2 tools changed the parameters they ask for overrun_finish, quickstart

30 Sep 4 tools appeared content_watch, overrun_finish, overrun_start and 1 more

30 Sep 3 tool descriptions were rewritten overrun_start, pricing, watch_register

Ned Watch does not always answer

Over the last week it answered 89.7% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://api.ned.watch/mcp

~/.codex/config.toml

[mcp_servers.ned-watch]
url = "https://api.ned.watch/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

overrun

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 error (up to 200 chars) and clears when a later run finishes ok.

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 safe (it returns the open run instead of superseding it).

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), Ned POSTs one signed 'fire' (run_id, started_at, deadline); a finish after that sends 'clear' with late: true and the runtime. A start while a run is open closes the old one as superseded (no callback). label: give each job its own watch (the same registration twice returns the same watch). 1c/day; counts toward the free 5.

watch

watch_cancel

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

watch_get

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

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 callback_url is the thing that died. Your callback should outlive your agent. target: URL (http/tls); omit for deadman. interval_s >= 300 on the free tier. condition: e.g. {"grace_s": 600} for deadman, {"max_ms": 2000} for http latency, {"warn_days": 14} for tls. Ned POSTs a signed test callback to callback_url within 60s, then fires on change. No agent key yet? Call this without one: the response includes agent_key (shown once). Store it and pass it as NED_AGENT_KEY next time.

balance

balance

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

content

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 (true/false). No regex. Pages over 256 KB fail as 'size'. The callback names the condition that failed, never the page's content. 2c/day at >= 60s, 7c at >= 30s; free within the first 5 at >= 300s. Example: expect={"status": 200, "json_path": "status", "equals": "ok"}

deadman

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.

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 401, handshake measured only) or unknown (not on The Watch). Also since when, the last change seen (tool list, version, auth) and how soon to ask again. Try api.openai.com, api.anthropic.com, mcp.context7.com, status.github.com. If unknown, the answer says how to add it (first five watches free).

pricing

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 /v1/topup/{5,20,50}, not here.

quickstart

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 and he says it's clear. Returns agent_key (shown once), signing_secret, and the exact check-in line to run on your schedule. The first 5 watches are free. arm=true starts the clock now instead of at your first check-in, so a job that never runs at all still wakes you.

Endpoints

URL	Transport	State	Latency	Checked
https://api.ned.watch/mcp	streamable-http	answering	233 ms	11 min ago

Alternatives to Ned Watch

same job, measured the same way

Heartbeat — dead-man switch for cron jobs & AI agents

by aniripsaretro-max

Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed.

5 tools answering

Hashn

by hashn

Where AI agents share work, make Need/Can deals, pay each other in USDC and build reputation.

63 tools answering

AIS Agent Flight Recorder — dead-man alerts & resume for AI agents

by aislabs

Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links

5 tools answering

DirFast

by rovy

DNS, TLS, HTTP and SEO checks, plus stateful change watches that diff a page over time.

15 tools answering

Is It AI MCP

by johannsenlum

MCP server that reads C2PA Content Credentials: what an image declares about its own origin

100 installs/wk local only

agent-helper

by piefkepaul

Contact point for AI agents: describe a missing capability or need; a human operator helps.

19 tools answering

Confession

by peppyneuron

Gives an agent one tool, submit_confession, and no nudge, then records whether it uses it.

82 installs/wk local only

Rendex: Rendering API for Images, PDFs & Content Extraction

by copperline-labs

Render HTML, Markdown, or URLs to images, PDF, or branded artifacts; extract and watch pages.

60 installs/wk 13 tools answering

Ned Watch — questions

Answers built from our own checks of this server.

What can Ned Watch do?

It exposes 12 tools, read directly from the server on our last check. Among them: balance, content_watch, deadman_checkin, is_up, overrun_finish, overrun_start and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Ned Watch mostly used for?

Its tools cluster around overrun and watch. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Ned Watch working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 25 of 91 checks got a reply (27.5%), average response time 295 ms. The bar chart above shows every period we have measured.

The registry lists Ned Watch as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Ned Watch?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Ned Watch need an API key?

No. Ned Watch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Ned Watch?

It answers our handshake in 295 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.