# 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

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-email-uptime-web-reader/mcp-email-uptime-web-reader.md), [page](https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-email-uptime-web-reader/mcp-email-uptime-web-reader)

## Channel facts

- Endpoint: `https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
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'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "type": "http",
      "url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-x402-bazaar-rank-worker-x402-bazaar-]
url = "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "type": "remote",
      "url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-x402-bazaar-rank-worker-x402-bazaar- --url 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-x402-bazaar-rank-worker-x402-bazaar-:
    url: "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "Transport": "http",
      "Url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-x402-bazaar-rank-worker-x402-bazaar- -t streamable-http -u 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "type": "http",
      "url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 70, +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.

### 2026-11-18 (score 69, +1)

- [security] Tool “doc_read” rewrote its description, which is the text the model reads

### 2026-11-16 (score 68, +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.

### 2026-11-14 (score 67, +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.

### 2026-11-13 (score 66, +1)

- [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
- [functional improvement] Schema quality: 251 → 191

### 2026-11-12 (score 65, +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.

### 2026-11-10 (score 64, +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.

### 2026-11-08 (score 63, 0)

- [security] 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
- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `check_email_address` (~158 tokens)

Check email address

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.

Input parameters:

- `email` (string, required): email address to check, e.g. name@example.org

### `check_email_batch` (~132 tokens)

Check email batch

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.

Input parameters:

- `emails` (array, required): 1 to 25 email addresses to check; duplicates are removed

### `url_uptime_ping` (~161 tokens)

URL uptime ping

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.

Input parameters:

- `url` (string, required): public http or https URL to check, e.g. https://example.com/ (ports 80, 443, 8080, 8443)

### `url_uptime_ping_batch` (~145 tokens)

URL uptime ping batch

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.

Input parameters:

- `urls` (array, required): 1 to 10 URLs; duplicates are removed

### `doc_read` (~150 tokens)

Doc read

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.

Input parameters:

- `max_chars` (integer): longest markdown to return; longer pages are cut and marked truncated
- `url` (string, required): public http or https page to read, e.g. https://example.com/

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-email-uptime-web-reader/mcp-email-uptime-web-reader#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 65
- 2026-11-11: 64
- 2026-11-10: 64
- 2026-11-09: 63
- 2026-11-08: 63
- 2026-11-07: 63

## Common questions

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

## Links

- Remote endpoint: https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader
- Website: https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/tools#email-uptime-web-reader
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-email-uptime-web-reader/mcp-email-uptime-web-reader.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-email-uptime-web-reader/mcp-email-uptime-web-reader/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-email-uptime-web-reader/mcp-email-uptime-web-reader.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-email-uptime-web-reader/mcp-email-uptime-web-reader
