# Watch (remote · watch.darmousseh.com)

Watch a web page, CSS selector, JSON value or price for weeks; poll changes or get signed webhooks.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `watch.darmousseh.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-darmousseh-watch/watch.md), [page](https://verifymcp.io/servers/com-darmousseh-watch/watch)

## Channel facts

- Endpoint: `https://watch.darmousseh.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.1.0`

## 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-11-21.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 546 tokens (~91/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete-watch" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

Watch is a hosted endpoint at https://watch.darmousseh.com/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 com-darmousseh-watch 'https://watch.darmousseh.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-darmousseh-watch": {
      "url": "https://watch.darmousseh.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-darmousseh-watch]
url = "https://watch.darmousseh.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-darmousseh-watch:
    url: "https://watch.darmousseh.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-darmousseh-watch": {
      "type": "http",
      "url": "https://watch.darmousseh.com/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-11-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 66, +38)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 95
- [functional] First check of Destructive annotations: 0
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-11-08 (score 28)

First indexed and scored.

## MCP tools (6)

### `ping` (~23 tokens)

Check the key works and show its plan limits. Read-only; creates nothing.

### `create-watch` (~257 tokens)

Start watching a URL; checks it on a schedule and records changes. Does one check now to set the baseline; does not notify for the baseline. Give at most one of keyword or condition+threshold, and one of selector or json_path.

Input parameters:

- `condition` (string): with threshold: alert when the first number found crosses it
- `email` (string): address to email on each change
- `idempotency_key` (string): same key replays the first result instead of creating a second watch
- `interval_min` (integer): minutes between checks, default 60 on free
- `json_path` (string): path into a JSON response, e.g. data.items[0].price
- `keyword` (string): alert when this text appears or disappears (case-insensitive)
- `name` (string): label shown in change summaries
- `regex` (string): narrow the extracted text; first capture group (or whole match) is compared
- `selector` (string): CSS selector to watch just part of an HTML page
- `threshold` (number)
- `url` (string, required): public http(s) page or JSON endpoint
- `webhook_url` (string): https URL to receive signed change events

### `list-watches` (~52 tokens)

List your watches, newest first, 10 per page. Read-only.

Input parameters:

- `cursor` (string): next_cursor from the previous page
- `limit` (integer): 1-50, default 10

### `get-watch` (~37 tokens)

Show one watch with its last value, status and webhook secret. Read-only.

Input parameters:

- `id` (string, required): watch id, starts with w_

### `delete-watch` (~47 tokens)

Stop and remove a watch. Its recorded changes stay readable. Cannot be undone.

Input parameters:

- `id` (string, required): watch id
- `idempotency_key` (string): safe-retry key

### `list-changes` (~98 tokens)

List recorded changes. With no cursor returns the 10 newest; with since returns changes after that cursor, oldest first, for polling. Read-only.

Input parameters:

- `before` (integer): older_cursor, to page back through history
- `limit` (integer): 1-50, default 10
- `since` (integer): cursor from a previous response; returns only newer changes
- `watch_id` (string): limit to one watch

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 70
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 67
- 2026-11-11: 67
- 2026-11-10: 66
- 2026-11-09: 28
- 2026-11-08: 28

## Common questions

### What is the Watch MCP server?

Watch is an MCP server listed in the public MCP registry as com.darmousseh/watch. Watch a web page, CSS selector, JSON value or price for weeks; poll changes or get signed webhooks. This page covers its hosted endpoint (https://watch.darmousseh.com/mcp).

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

Watch scores 71 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 Watch MCP server expose?

Watch exposes 6 tools: ping, create-watch, list-watches, get-watch, delete-watch, list-changes. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.

### Does the Watch MCP server require authentication?

Yes. Watch asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Watch MCP server still maintained?

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

### What did VerifyMCP test on the Watch MCP server?

VerifyMCP ran 12 checks on Watch, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Watch: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://watch.darmousseh.com/mcp
- Authorisation metadata: https://watch.darmousseh.com/.well-known/oauth-protected-resource/mcp
- Website: https://watch.darmousseh.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-darmousseh-watch/watch.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-darmousseh-watch/watch/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-darmousseh-watch/watch.json
- HTML version of this page: https://verifymcp.io/servers/com-darmousseh-watch/watch
