Watch

com.darmoussehPublished by darmousseh.comOfficial publisherv1.1.0Updated Nov 8, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowWeb Search & Scraping

Overview

AI-generated overview

Remote MCP server that lets an assistant set up long-running watches on web pages, CSS selectors, JSON values or prices and report changes.

What you can do
  • Create watches on a web page, CSS selector, JSON value or price
  • Keep watches running for weeks and check them for changes
  • Poll for detected changes or receive signed webhook notifications
  • No tool list is published, so exact operations are not documented
When to use it
Useful when you want an assistant to track a page, element, JSON field or price over time and be told when it changes, instead of checking manually.
Requirements
A remote endpoint at watch.darmousseh.com over streamable HTTP. A bearer API key is required in the Authorization header; the provider says a free key is available via signup on its site.
Before you install
The Authorization header carries a secret API key, so keep it private and scope it as narrowly as the service allows. Watches run for weeks and may send signed webhooks to a URL you supply; review what data leaves your side and where webhooks are delivered.

Installation

In SourceWeft

  1. Open Watch in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/com.darmousseh%2Fwatch/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": {
    "watch": {
      "type": "http",
      "url": "https://watch.darmousseh.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestNov 8, 2026

Score

56% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

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