x402 Markdown Reader MCP server
dev.workers.xbtbot.x402-reader/markdown-readerx402-reader.xbtbot.workers.devstreamable-httpv1.0.0Scanned
Turn any public web page into clean Markdown. Pay-per-call via x402: 0.005 USDC on Base.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the x402 Markdown Reader MCP server can do
The x402 Markdown Reader MCP server is published by x402-reader.xbtbot.workers.dev, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: check_domains), but cannot delete data. 1 tool only reads.
2 tools bring in text other people can write (read_url and check_domains); 1 tool can send data out of your system (read_url).
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.
Last scanned Nov 15, 2026, version 1.0.0.
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.
2 tools
Changes things 1Claude Code: ask
check_domainsCheck domain name availability via public registry RDAP for .xyz .com .io .ai .app .dev, plus variations (get-, -hq, -labs, try-).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 Check domain name availability via public registry RDAP for .xyz .com .io .ai .app .dev, plus variations (get-, -hq, -labs, try-). 404 from the registry = likely available. Not a registrar quote; confirm at checkout. PAID via x402: 0.005 USDC on Base per call; call without x_payment to get requirements.
Annotations the server declares
- title: Check domain availability (x402, 0.005 USDC)
- readOnlyHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
read_urlFetch a public web page and return clean Markdown of its main content (title, byline, excerpt, markdown).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "read_url" says "read": 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 "read_url" says "read" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "fetch" and "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 Fetch a public web page and return clean Markdown of its main content (title, byline, excerpt, markdown). PAID via x402: 0.005 USDC on Base per successful call. Call without x_payment to get the exact x402 payment requirements; sign them with an x402 client (exact scheme, EIP-3009 USDC transferWithAuthorization) and call again with the base64 PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1) value in x_payment. You are only charged if extraction succeeds.
Annotations the server declares
- title: Read URL as Markdown (x402, 0.005 USDC)
- readOnlyHint: 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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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 20, 2026, 18:53 UTC, unchanged since Oct 22, 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
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://x402-reader.xbtbot.workers.dev/mcp: tools/list returned 2 tools to an anonymous client, including check_domains (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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http markdown-reader https://x402-reader.xbtbot.workers.dev/mcpclaude mcp add --transport http markdown-reader https://x402-reader.xbtbot.workers.dev/mcpRun 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__markdown-reader__read_url",
"mcp__markdown-reader__check_domains"
],
"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 markdown-reader. Review it before you use it.
Capability tags behind 2 rules
- mcp__markdown-reader__read_url untrusted-input, outbound
- mcp__markdown-reader__check_domains untrusted-input
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.xbtbot.x402-reader/markdown-reader/verify?hash=fa3d54141fe05517d3a08ec4510e20419fcf5bc0af6720c580b60f7ed32f3a3d" | jq -e '.changed == false'Pinned hash fa3d54141fe0, from Nov 15, 2026, 05:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.xbtbot.x402-reader/markdown-reader/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.xbtbot.x402-reader/markdown-reader)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
x402 Markdown Reader MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the x402 Markdown Reader MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 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 x402 Markdown 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 x402 Markdown 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 x402 Markdown Reader MCP server have?
- 2 tools: 1 write, 1 read. check_domains and read_url.
Does the x402 Markdown Reader MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the x402 Markdown Reader MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): read_url.
Has the x402 Markdown Reader MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.