P0: email check, uptime, web reader
REMOTE · X402-BAZAAR-RANK.X402-BAZAAR-RANK-WORKER.WORKERS.DEV
Email address checks, URL uptime pings and web page to markdown for agents, pay per call
Available components
Last scanned (21 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 937 tokens (~187/item across 5 items; 5 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 Management47
- Stability observed for 14 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Tool “doc_read” rewrote its description, which is the text the model reads security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
- Tool “check_email_address” rewrote its description, which is the text the model reads security
- Tool “check_email_batch” rewrote its description, which is the text the model reads security
- Tool “doc_read” rewrote its description, which is the text the model reads security
- Tool “url_uptime_ping” rewrote its description, which is the text the model reads security
- Tool “url_uptime_ping_batch” rewrote its description, which is the text the model reads security
- Schema quality: 251 → 191 ▲ functional
- 12 Nov 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.
- 10 Nov 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.
- 8 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_email_address” rewrote its description, which is the text the model reads security
- Tool “check_email_batch” rewrote its description, which is the text the model reads security
- Tool “doc_read” rewrote its description, which is the text the model reads security
- Tool “url_uptime_ping” rewrote its description, which is the text the model reads security
- Tool “url_uptime_ping_batch” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402-bazaar-rank-worker.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6c09b073fe5d3fd83fd987465725765b6e5 |
| SANs: *.x402-bazaar-rank-worker.workers.dev, x402-bazaar-rank-worker.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 x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader | Verified | 200 | |
| http (plaintext) | http://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader | Served over HTTP | 200 |
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 →
check_email_address Check email address ~158
Use when you need to check an email address before sending, signing up a user or adding a lead: syntax (IDN-aware), MX records with A/AAAA fallback, null MX, and disposable, role (info@, sales@). Returns the paid x402 request for your input (GET /v1/email/verify, $0.01 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Checks one mailbox; for a list use check_email_batch. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | email address to check, e.g. name@example.org |
No output schema declared.
No examples provided.
check_email_batch Check email batch ~132
Use when you need to check a list of email addresses before a mailing or import: up to 25 addresses in one POST, each checked exactly like /v1/email/verify. Returns the paid x402 request for your input (POST /v1/email/verify/batch, $0.25 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one address use check_email_address.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | 1 to 25 email addresses to check; duplicates are removed |
No output schema declared.
No examples provided.
doc_read Doc read ~150
Use for reading a web page as clean markdown for an LLM or agent (url to markdown, reader, html to text): POST {url, max_chars} and get {title, markdown, chars, source_url}. Returns the paid x402 request for your input (POST /v1/doc/read, $0.005 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | longest markdown to return; longer pages are cut and marked truncated |
| url | string | yes | public http or https page to read, e.g. https://example.com/ |
No output schema declared.
No examples provided.
url_uptime_ping URL uptime ping ~161
Use when you need to know if a URL is up right now (uptime ping, health check, link check): one HEAD request from a Cloudflare edge, up to 4 redirects; returns ok, status, latency_ms, tls. Returns the paid x402 request for your input (GET /v1/uptime/ping, $0.01 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For several URLs use url_uptime_ping_batch.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | public http or https URL to check, e.g. https://example.com/ (ports 80, 443, 8080, 8443) |
No output schema declared.
No examples provided.
url_uptime_ping_batch URL uptime ping batch ~145
Use when you monitor several endpoints: up to 10 http(s) URLs in one POST, each checked exactly like /v1/uptime/ping (status, latency, redirects, TLS, server) from Cloudflare's edge. Returns the paid x402 request for your input (POST /v1/uptime/ping/batch, $0.10 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one URL use url_uptime_ping.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | 1 to 10 URLs; duplicates are removed |
No output schema declared.
No examples provided.
How do I install the P0: email check, uptime, web reader MCP server?
P0: email check, uptime, web reader is a hosted endpoint at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader, 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 · x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev
claude mcp add --transport http dev-workers-x402-bazaar-rank-worker-x402-bazaar- 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader'
What is the P0: email check, uptime, web reader MCP server?
P0: email check, uptime, web reader is an MCP server listed in the public MCP registry as dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/email…. Email address checks, URL uptime pings and web page to markdown for agents, pay per call. This page covers its hosted endpoint (https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader).
Is the P0: email check, uptime, web reader MCP server safe to use?
P0: email check, uptime, web reader scores 70 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 P0: email check, uptime, web reader MCP server expose?
P0: email check, uptime, web reader exposes 5 tools: check_email_address, check_email_batch, url_uptime_ping, url_uptime_ping_batch, doc_read. Their descriptions and schemas cost roughly 746 tokens of context every time the server is loaded.
Does the P0: email check, uptime, web reader MCP server require authentication?
No. We connected to P0: email check, uptime, web reader without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the P0: email check, uptime, web reader MCP server still maintained?
P0: email check, uptime, web reader is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the P0: email check, uptime, web reader MCP server?
VerifyMCP ran 13 checks on P0: email check, uptime, web reader, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.