well-009-url-change-watch
REMOTE · WELL-009-URL-CHANGE-WATCH.MMELNYK2000.WORKERS.DEV
Has this https URL changed? (sha256/etag). x402 $0.01 USDC, Base. As is, no warranty.
Available components
Last scanned (7 hours ago)
Scores higher than 59% of remote servers
Unreachable for 2 days in a row. Last reached 21 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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 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.mmelnyk2000.workers.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of well-009-url-change-watch.mmelnyk2000.workers.dev. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| well-009-url-change-watch.mmelnyk2000.workers.dev. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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.mmelnyk2000.workers.dev/mcp | Unreachable | ||
| http (plaintext) | http://well-009-url-change-watch.mmelnyk2000.workers.dev/mcp | HTTPS enforced |
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.mmelnyk2000.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.mmelnyk2000.workers.dev
claude mcp add --transport http dev-workers-mmelnyk2000-well-009-url-change-watc 'https://well-009-url-change-watch.mmelnyk2000.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.mmelnyk2000.well-009-url-change-watch/url-chang…. 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.mmelnyk2000.workers.dev/mcp).
Is the well-009-url-change-watch MCP server safe to use?
well-009-url-change-watch scores 69 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?
Its publisher declares no required credentials for well-009-url-change-watch. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the well-009-url-change-watch MCP server still maintained?
well-009-url-change-watch is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 21 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.