well-009-url-change-watch

dev.workers.mmelnyk2000.well-009-url-change-watchPublished by well-009-url-change-watch.mmelnyk2000.workers.devOfficial publisherv1.0.0Updated Oct 24, 2026

Has this https URL changed? (sha256/etag). x402 $0.01 USDC, Base. As is, no warranty.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint that checks whether a given HTTPS URL's content has changed, using a SHA-256 hash or ETag.

What you can do
Check whether a supplied HTTPS URL's content has changed since a previous check, comparing a SHA-256 hash or ETag. Report the current hash or ETag value for a URL so an assistant can track changes over time.
When to use it
Useful when you want an assistant to watch a specific web page or resource for changes and report whether its content differs from an earlier state.
Requirements
Remote streamable HTTP endpoint; no authentication, environment variables or headers declared. A payment of $0.01 USDC on Base (x402) is stated for use.
Before you install
The description states a per-use charge of $0.01 USDC on Base via x402, so using it involves spending cryptocurrency; be aware of wallet and payment handling. The service is offered as is with no warranty, and the URLs you submit are sent to a third-party endpoint.

Installation

In SourceWeft

  1. Open well-009-url-change-watch 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.mmelnyk2000.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": {
    "well-009-url-change-watch": {
      "type": "http",
      "url": "https://well-009-url-change-watch.mmelnyk2000.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 16, 2026

Score

17% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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