# Ned Watch (remote · api.ned.watch)

Wake me when my agent misses its heartbeat: one quickstart call. HTTP, TLS, deadman; US+EU nodes.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `api.ned.watch`: 63/100 (this document), [markdown](https://verifymcp.io/servers/watch-ned-ned-watch/api.md), [page](https://verifymcp.io/servers/watch-ned-ned-watch/api)

## Channel facts

- Endpoint: `https://api.ned.watch/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 588 tokens (~84/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Ned Watch MCP server?

Ned Watch is a hosted endpoint at https://api.ned.watch/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "watch-ned-ned-watch": {
      "type": "remote",
      "url": "https://api.ned.watch/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add watch-ned-ned-watch --url 'https://api.ned.watch/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  watch-ned-ned-watch:
    url: "https://api.ned.watch/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "watch-ned-ned-watch": {
      "Transport": "http",
      "Url": "https://api.ned.watch/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add watch-ned-ned-watch -t streamable-http -u 'https://api.ned.watch/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 63)

First indexed and scored.

## MCP tools (7)

### `watch_register` (~174 tokens)

Register a watch. type: http | tls | deadman. target: URL (http/tls); omit for deadman.
    interval_s >= 300 on the free tier. condition: e.g. {"warn_days": 14} for tls, {"grace_s": 600} for deadman,
    {"max_ms": 2000} for http latency. 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.

Input parameters:

- `callback_url` (string, required)
- `condition`
- `interval_s` (integer)
- `target`
- `type` (string, required)

### `quickstart` (~126 tokens)

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.

Input parameters:

- `callback_url` (string, required)
- `every_minutes` (integer)

### `watch_get` (~37 tokens)

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

Input parameters:

- `watch_id` (string, required)

### `watch_cancel` (~29 tokens)

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

Input parameters:

- `watch_id` (string, required)

### `deadman_checkin` (~78 tokens)

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.

Input parameters:

- `signing_secret` (string, required)
- `watch_id` (string, required)

### `balance` (~29 tokens)

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

### `pricing` (~86 tokens)

Ned Watch pricing: 5 free watches at >=300s, then per-day rates (http/tls 2c, fast 7c, deadman 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/watch-ned-ned-watch/api#diagnostics

## Score history

- 2026-09-29: 63

## Common questions

### What is the Ned Watch MCP server?

Ned Watch is an MCP server listed in the public MCP registry as watch.ned/ned-watch. Wake me when my agent misses its heartbeat: one quickstart call. HTTP, TLS, deadman; US+EU nodes. This page covers its hosted endpoint (https://api.ned.watch/mcp).

### Is the Ned Watch MCP server safe to use?

Ned Watch scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Ned Watch MCP server expose?

Ned Watch exposes 7 tools: watch_register, quickstart, watch_get, watch_cancel, deadman_checkin, and 2 more. Their descriptions and schemas cost roughly 559 tokens of context every time the server is loaded.

### Does the Ned Watch MCP server require authentication?

No. We connected to Ned Watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Ned Watch MCP server still maintained?

Ned Watch is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.ned.watch/mcp
- Website: https://ned.watch/
- Changelog RSS feed: https://verifymcp.io/servers/watch-ned-ned-watch/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/watch-ned-ned-watch/api.json
- HTML version of this page: https://verifymcp.io/servers/watch-ned-ned-watch/api