url-change-watch: did this page change?
Server Details
Did this page change? Hash-compare any public URL vs last check; skip unchanged re-reads. x402 $0.01
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between overlapping tools. Its purpose—comparing a stored sha256/etag against a live URL—is stated unambiguously in the name and description.
A single tool named url-change-check uses a clear, descriptive kebab-case convention that matches the server name (url-change-watch). There is no competing convention to create inconsistency.
The server is a narrow single-capability paid endpoint (one HTTP fetch-and-compare), so a single tool is genuinely the right scope rather than a symptom of an incomplete surface. It is on the thin side by general standards, but nothing more is needed for this atomic operation.
The tool covers both the initial check (no previous hash supplied) and subsequent comparisons via optional previous_sha256/previous_etag, and returns a new hash plus optional changed body so the agent can close the loop. Optional parameters and documented caps/timeouts leave no obvious dead ends within the stated stateless-hash-comparison domain.
Available Tools
1 toolurl-change-checkARead-onlyIdempotentInspect
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.
Inputs: url (required), previous_etag, previous_sha256, include_body_if_changed.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Deterministic webpage change detection, hashes and text diffs for recurring monitoring via x402 MCP.
Has this https URL changed? (sha256/etag). x402 $0.01 USDC, Base. As is, no warranty.
Before your agent pays an x402 URL, see whether vet402 paid it and got the content back.
Watch a public web page for changes when your agent cannot stay running. Hourly checks, signed diffs
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceA shared URL-freshness oracle for AI agents. Returns REUSE, REFETCH, or UNKNOWN before an agent pays to retrieve a URL again.-
- FlicenseNot gradedqualityNot gradedmaintenanceURL reality check for AI agents — returns HTTP status, SHA-256 content hash, classification, readability score, title, and wayback-machine fallback when dead, cached 10 minutes at $0.001 per call.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to inspect a URL for reachability, then extract clean structured Markdown, headings, and links from public web pages, paid per successful request via x402 micropayments with no accounts or API keys.MIT
- AlicenseNot gradedqualityDmaintenanceRead-only observation of a single live URL: parses static HTML to report security posture, forms, links, accessibility signals, and leaks, with described fixes. SSRF-gated and safe, never executes JavaScript.85 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.