Ned Watch
REMOTE · API.NED.WATCH · SCANNED SEP 29
Wake me when my agent misses its heartbeat: one quickstart call. HTTP, TLS, deadman; US+EU nodes.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 588 tokens (~84/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
remote · api.ned.watch
claude mcp add --transport http watch-ned-ned-watch 'https://api.ned.watch/mcp'
{
"mcpServers": {
"watch-ned-ned-watch": {
"url": "https://api.ned.watch/mcp"
}
}
} {
"servers": {
"watch-ned-ned-watch": {
"type": "http",
"url": "https://api.ned.watch/mcp"
}
}
} [mcp_servers.watch-ned-ned-watch] url = "https://api.ned.watch/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"watch-ned-ned-watch": {
"type": "remote",
"url": "https://api.ned.watch/mcp",
"enabled": true
}
}
} openclaw mcp add watch-ned-ned-watch --url 'https://api.ned.watch/mcp' --transport streamable-http
mcp_servers:
watch-ned-ned-watch:
url: "https://api.ned.watch/mcp" {
"McpServers": {
"watch-ned-ned-watch": {
"Transport": "http",
"Url": "https://api.ned.watch/mcp"
}
}
} assistant mcp add watch-ned-ned-watch -t streamable-http -u 'https://api.ned.watch/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://api.ned.watch/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ned.watch | CN=YE2,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 65a45f572e6d4c84a4e0a2452a5f7f4d607 |
| SANs: *.ned.watch, ned.watch | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.ned.watch. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| watch. | present | 54769 | 8 | Verified |
| ned.watch. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ned.watch/mcp | Verified | 200 | |
| http (plaintext) | http://api.ned.watch/mcp | HTTPS enforced | 308 | https://api.ned.watch/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
balance ~29
Your balance in cents, free allowance used, burn per day, days left, and the top-up routes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deadman_checkin ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| signing_secret | string | yes | – |
| watch_id | string | yes | – |
No output schema declared.
No examples provided.
pricing ~86
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quickstart ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | yes | – |
| every_minutes | integer | – | – |
No output schema declared.
No examples provided.
watch_cancel ~29
Cancel a watch you registered. Frees a free-tier slot.
| Name | Type | Req | Description |
|---|---|---|---|
| watch_id | string | yes | – |
No output schema declared.
No examples provided.
watch_get ~37
Current state of one of your watches: status, fired, fire_count, next_check, last_state.
| Name | Type | Req | Description |
|---|---|---|---|
| watch_id | string | yes | – |
No output schema declared.
No examples provided.
watch_register ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | yes | – |
| condition | – | – | – |
| interval_s | integer | – | – |
| target | – | – | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
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.