well-009-url-change-watch
REMOTE · WELL-009-URL-CHANGE-WATCH.RAINMAKER-WELLS.WORKERS.DEV
Has this https URL changed? (sha256/etag). x402 $0.01 USDC, Base. As is, no warranty.
Available components
Last scanned (3 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Monitoring and Observability
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 261 tokens (~261/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 22 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 66
First indexed and scored.
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 23 Oct 2026 · Probed https://well-009-url-change-watch.rainmaker-wells.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rainmaker-wells.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6cb2a7f8727626e5d6e7b9a63ee02f829b9 |
| SANs: *.rainmaker-wells.workers.dev, rainmaker-wells.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of well-009-url-change-watch.rainmaker-wells.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://well-009-url-change-watch.rainmaker-wells.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://well-009-url-change-watch.rainmaker-wells.workers.dev/mcp | Inconclusive | 406 |
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 →
url-change-check ~261
Fetch a public https URL, compute SHA-256 of the response body, and report whether it changed vs a prior sha256/etag ($0.01 USDC via x402). Sticky: store sha256 and call again later. Optional previous_sha256, previous_etag, include_body_if_changed. https only — http, file, data, localhost, and private IPs rejected. Caps: 1 MB body, ~10s timeout, max 5 redirects. Returns JSON { url, final_url, content_type, byte_length, sha256, etag?, last_modified?, changed, warnings, body_preview? }. As is, no warranty. Nothing stored.
| Name | Type | Req | Description |
|---|---|---|---|
| include_body_if_changed | boolean | – | If true and changed (or baseline), include truncated body text (~8KB) as body_preview. Default false. |
| previous_etag | string | – | Prior ETag; used when previous_sha256 is absent and response has ETag (quotes normalized). |
| previous_sha256 | string | – | Hex SHA-256 of last seen body. If omitted (and no previous_etag match), this call is a baseline (changed=null). |
| url | string | yes | https URL to watch. http/file/data/localhost/private IPs rejected. |
No output schema declared.
No examples provided.
How do I install the well-009-url-change-watch MCP server?
well-009-url-change-watch is a hosted endpoint at https://well-009-url-change-watch.rainmaker-wells.workers.dev/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 · well-009-url-change-watch.rainmaker-wells.workers.dev
claude mcp add --transport http dev-workers-rainmaker-wells-well-009-url-change- 'https://well-009-url-change-watch.rainmaker-wells.workers.dev/mcp'
What is the well-009-url-change-watch MCP server?
well-009-url-change-watch is an MCP server listed in the public MCP registry as dev.workers.rainmaker-wells.well-009-url-change-watch/url-c…. Has this https URL changed? (sha256/etag). x402 $0.01 USDC, Base. As is, no warranty. This page covers its hosted endpoint (https://well-009-url-change-watch.rainmaker-wells.workers.dev/mcp).
Is the well-009-url-change-watch MCP server safe to use?
well-009-url-change-watch scores 67 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 well-009-url-change-watch MCP server expose?
well-009-url-change-watch exposes 1 tool: url-change-check. Their descriptions and schemas cost roughly 261 tokens of context every time the server is loaded.
Does the well-009-url-change-watch MCP server require authentication?
No. We connected to well-009-url-change-watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the well-009-url-change-watch MCP server still maintained?
well-009-url-change-watch is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.