url-change-watch: did this page change?

dev.workers.rainmaker-wells.well-009-url-change-watchPublished by well-009-url-change-watch.rainmaker-wells.workers.devOfficial publisherv1.0.1Updated Nov 4, 2026

Did this page change? Hash-compare any public URL vs last check; skip unchanged re-reads. x402 $0.01

VerifiedStreamable HTTPWeb executable

Overview

url-change-watch: did this page change?'s hosted MCP server (well-009-url-change-watch.rainmaker-wells.workers.dev), published by well-009-url-change-watch.rainmaker-wells.workers.dev; no sign-in required; Streamable HTTP; 1 tool.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
well-009-url-change-watch.rainmaker-wells.workers.dev
Endpoint
well-009-url-change-watch.rainmaker-wells.workers.dev
Last checked

Installation

In SourceWeft

  1. Open url-change-watch: did this page change? in the dashboard and add it to a workspace.
  2. 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/dev.workers.rainmaker-wells.well-009-url-change-watch%2Furl-change-check/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": {
    "url-change-watch-did-this-page-change": {
      "type": "http",
      "url": "https://well-009-url-change-watch.rainmaker-wells.workers.dev/mcp"
    }
  }
}

Tools

1

url-change-check

URL change check

Change detection for agents ($0.01 USDC via x402). Pass a public https URL plus the sha256/etag from your last check; get changed true/false and the new hash. Use it to watch pricing pages, docs, terms of service, or job and grant listings, and only run the expensive LLM read when something actually changed. Stateless: you keep the hash. Optional previous_sha256, previous_etag, include_body_if_changed. https only; caps 1 MB body, ~10s timeout, 5 redirects. As is, no warranty. As is, no warranty. Nothing stored.

Parametersurlrequiredprevious_etagprevious_sha256include_body_if_changed

Version history

2
  1. v1.0.1LatestNov 4, 2026
  2. v1.0.0Oct 21, 2026

Score

72% 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 listedRequired15 pts
  • 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.