Ned Watch

watch.nedPublished by ned.watchOfficial publisherv1.2.0Updated Oct 25, 2026

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

The publisher's own server: watch.diy – DIY Store Finder

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Ned Watch is a remote uptime and heartbeat monitoring service that lets an assistant register watches, check in on deadman timers, and read status and balance.

What you can do
Register and cancel deadman, overrun, HTTP, TLS and content watches, with optional webhook notifications to Discord, Slack or Teams and a callback URL for signed fire and clear messages. Check in on deadman watches and start or finish overrun runs to signal that a job began or ended. Read the current state of a watch, including status, fire count and next check. Query public reachability of a host and its subdomains from two continents. Check balance, free allowance used and pricing.
When to use it
Use it when an assistant or scheduled job needs an external watchdog that notices a missed heartbeat, a run exceeding its deadline, or a URL returning the wrong status or content, and alerts a human through webhooks or a callback.
Requirements
Remote streamable HTTP endpoint at api.ned.watch; no local runtime. An agent key is sent as an Authorization bearer header; the first watch_register or quickstart call can be made without one and returns the key. Some calls instead use a watch's signing secret as the bearer token. A callback URL reachable by the service is needed for alerts.
Before you install
The agent key and each watch's signing secret are credentials; the key is shown once, so store it safely. Registering watches creates persistent monitoring and may consume free-tier slots or prepaid balance. Top-ups are paid in USDC on Base through x402, which spends real funds; pricing and balance tools only report, and payment happens outside this server. Callback and webhook URLs receive signed messages, so point them only at endpoints you control.

Installation

In SourceWeft

  1. Open Ned Watch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/watch.ned%2Fned-watch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

12

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).

Parametershostrequired

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.

Parameterstyperequirednotifytargetconditioninterval_scallback_urlrequired

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.

Parametersarmcallback_urlrequiredevery_minutes

watch_get

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

Parameterswatch_idrequired

watch_cancel

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

Parameterswatch_idrequired

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.

Parameterswatch_idrequiredsigning_secretrequired

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.

Parameterslabelcallback_urlrequiredmax_runtime_srequired

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).

Parametersrun_idwatch_idrequiredsigning_secretrequired

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.

Parameterserrorfailedrun_idwatch_idrequiredsigning_secretrequired

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"}

Parametersexpectrequiredtargetrequiredinterval_scallback_urlrequired

balance

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

Takes no parameters.

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.

Takes no parameters.

Version history

2
  1. v1.2.0LatestOct 1, 2026
  2. v1.1.1Sep 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Watch integrations