P0: email check, uptime, web reader MCP server
dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/email-uptime-web-readerx402-bazaar-rank.x402-bazaar-rank-worker.workers.devstreamable-httpv1.0.1Scanned
Email address checks, URL uptime pings and web page to markdown for agents, pay per call
5 tools: 2 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 5
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the P0: email check, uptime, web reader MCP server can do
The P0: email check, uptime, web reader MCP server is published by x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: check_email_address and check_email_batch), but cannot delete data. 3 tools only read.
1 tool reads private data (doc_read); 5 tools bring in text other people can write (check_email_address, check_email_batch, url_uptime_ping and 2 more); 3 tools can send data out of your system (url_uptime_ping, url_uptime_ping_batch and doc_read). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
check_email_addressUse when you must 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 (inf…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use when you must 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. With an access key (Authorization: Bearer p0k_..., buy at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) the tool pays the call itself, returns the data and deducts the price. First call each day returns the data itself, free; later calls return the paid request.
Annotations the server declares
- title: Check email address
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
check_email_batchUse when you must 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use when you must 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. With an access key (Authorization: Bearer p0k_..., buy at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) the tool pays the call itself, returns the data and deducts the price.
Annotations the server declares
- title: Check email batch
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
doc_readUse 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}.Reads private dataReads text others writeCan send data outNo findings
Why it is in this group
- The name "doc_read" says "read": a word for reading.
What it can reach
- private-dataThe name "doc_read" says "read" and "doc": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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. With an access key (Authorization: Bearer p0k_..., buy at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) the tool pays the call itself, returns the data and deducts the price. First call each day returns the data itself, free; later calls return the paid request.
Annotations the server declares
- title: Doc read
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
url_uptime_pingUse 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_…Reads text others writeCan send data outNo findings
Why it is in this group
- The name "url_uptime_ping" says "ping": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "url_uptime_ping" says "ping" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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. With an access key (Authorization: Bearer p0k_..., buy at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) the tool pays the call itself, returns the data and deducts the price.
Annotations the server declares
- title: URL uptime ping
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
url_uptime_ping_batchUse 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 edg…Reads text others writeCan send data outNo findings
Why it is in this group
- The name "url_uptime_ping_batch" says "ping": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "url_uptime_ping_batch" says "ping" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.urls), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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. With an access key (Authorization: Bearer p0k_..., buy at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) the tool pays the call itself, returns the data and deducts the price.
Annotations the server declares
- title: URL uptime ping batch
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
15 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__email-uptime-web-reader__doc_read"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:24 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/.well-known/oauth-protected-resource
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-reader: tools/list returned 5 tools to an anonymous client, including check_email_address (write), check_email_batch (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:check_email_addressChanges thingsdescription
- Changed:check_email_batchChanges thingsdescription
- Changed:doc_readOnly readsdescription
- Changed:url_uptime_pingOnly readsdescription
- Changed:url_uptime_ping_batchOnly readsdescription
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http email-uptime-web-reader https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-readerclaude mcp add --transport http email-uptime-web-reader https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/email-uptime-web-readerRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__email-uptime-web-reader__check_email_address",
"mcp__email-uptime-web-reader__check_email_batch",
"mcp__email-uptime-web-reader__url_uptime_ping",
"mcp__email-uptime-web-reader__url_uptime_ping_batch",
"mcp__email-uptime-web-reader__doc_read"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as email-uptime-web-reader. Review it before you use it.
Capability tags behind 5 rules
- mcp__email-uptime-web-reader__check_email_address untrusted-input
- mcp__email-uptime-web-reader__check_email_batch untrusted-input
- mcp__email-uptime-web-reader__url_uptime_ping untrusted-input, outbound
- mcp__email-uptime-web-reader__url_uptime_ping_batch untrusted-input, outbound
- mcp__email-uptime-web-reader__doc_read private-data, untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/email-uptime-web-reader/verify?hash=90ff04f068e5d1fcf50904700f8a8cc5ff2337bec2e68f2d92f1504818486376" | jq -e '.changed == false'Pinned hash 90ff04f068e5, from Nov 11, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/email-uptime-web-reader/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/email-uptime-web-reader)Source: MCP Registry. Synced Nov 11, 2026, 14:17 UTC.
P0: email check, uptime, web reader MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the P0: email check, uptime, web reader MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the P0: email check, uptime, web reader MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the P0: email check, uptime, web reader MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the P0: email check, uptime, web reader MCP server have?
- 5 tools: 2 write, 3 read. check_email_address, check_email_batch, url_uptime_ping, url_uptime_ping_batch and doc_read.
Does the P0: email check, uptime, web reader MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the P0: email check, uptime, web reader MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): url_uptime_ping, url_uptime_ping_batch and doc_read.
Has the P0: email check, uptime, web reader MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.