Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Watch

REMOTE · WATCH.DARMOUSSEH.COM

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

+3 this week 71 Trust /100

Last scanned (19 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Web Scraping

Trust breakdown (7 categories)

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 Security71
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 546 tokens (~91/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 +38
    • Transport: unverified → pass ▲ security
    • 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. security
    • MCP protocol: unverified → fail ▼ functional
    • 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 functional
  • 8 Nov 26 28

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://watch.darmousseh.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=darmousseh.com CN=WE1,O=Google Trust Services,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA256 75fdd8aa51400f1513529e8f92f8a0f1
SANs: darmousseh.com, watch.darmousseh.com, *.watch.darmousseh.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of watch.darmousseh.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
darmousseh.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer

Bearer

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://watch.darmousseh.com/mcp Verified 200
http (plaintext) http://watch.darmousseh.com/mcp Inconclusive 401
MCP tools · 6 exposed · ~514 tokens

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 →

Tool Tokens
create-watch ~257

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.

NameTypeReqDescription
conditionstring–with threshold: alert when the first number found crosses it
emailstring–address to email on each change
idempotency_keystring–same key replays the first result instead of creating a second watch
interval_mininteger–minutes between checks, default 60 on free
json_pathstring–path into a JSON response, e.g. data.items[0].price
keywordstring–alert when this text appears or disappears (case-insensitive)
namestring–label shown in change summaries
regexstring–narrow the extracted text; first capture group (or whole match) is compared
selectorstring–CSS selector to watch just part of an HTML page
thresholdnumber––
urlstringyespublic http(s) page or JSON endpoint
webhook_urlstring–https URL to receive signed change events

No output schema declared.

No examples provided.

delete-watch ~47

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

NameTypeReqDescription
idstringyeswatch id
idempotency_keystring–safe-retry key

No output schema declared.

No examples provided.

get-watch ~37

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

NameTypeReqDescription
idstringyeswatch id, starts with w_

No output schema declared.

No examples provided.

list-changes ~98

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

NameTypeReqDescription
beforeinteger–older_cursor, to page back through history
limitinteger–1-50, default 10
sinceinteger–cursor from a previous response; returns only newer changes
watch_idstring–limit to one watch

No output schema declared.

No examples provided.

list-watches ~52

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

NameTypeReqDescription
cursorstring–next_cursor from the previous page
limitinteger–1-50, default 10

No output schema declared.

No examples provided.

ping ~23

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · watch.darmousseh.com

# add to Claude Code
claude mcp add --transport http com-darmousseh-watch 'https://watch.darmousseh.com/mcp'
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.