Skip to content

readfetch MCP server

com.readfetch/mcp-x402-proxyreadfetch.comstreamable-httpv0.1.23Scanned

Stdio MCP proxy: free probe, then x402-paid ReadFetch tools; for hosts that cannot sign x402.

15 tools: 10 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 10 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 14
  • Can send data out · 12
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

10 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 readfetch MCP server can do

The readfetch MCP server is published by readfetch.com, a domain the MCP Registry verified. It has 15 tools. It can create or change data (10 tools: readfetch_text, readfetch_map, readfetch_scrape, readfetch_residential and 6 more), but cannot delete data. 5 tools only read.

14 tools bring in text other people can write (readfetch_text, readfetch_map, readfetch_scrape and 11 more); 12 tools can send data out of your system (readfetch_text, readfetch_map, readfetch_scrape and 9 more).

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 21, 2026, version 0.1.23.

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.

15 tools

Changes things 10Claude Code: ask
  • readfetch_batchPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Read a fixed list of public HTML pages in one call—the same article extraction as POST /v1/text for each URL (Markdown or plain text plus title and metadata). One x402 payment covers the batch (minimum 3 pages quoted; URLs deduped, max 50). Returns results in input order: each item has url, status_code, text, billed, and hint when undelivered, plus batch-level delivered, failed, billed_pages, and optional credit for unused pages. Undelivered pages are not billed. Use readfetch_text for one URL, readfetch_map then readfetch_crawl to discover and walk a site, readfetch_scrape when JavaScript is required. Read-only; 402 without PAYMENT-SIGNATURE like other paid tools.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/batch
  • readfetch_crawlPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo 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.
    • untrusted-inputThe name "readfetch_crawl" says "crawl": 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.
    Description, as the server wrote it
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Start a bounded async crawl from one seed URL. Returns job_id, status (queued), pages_quoted, and price_usd — then poll readfetch_crawl_status with that id until status is complete or failed. A complete job includes per-page url and Markdown in the status payload. Cap scope with max_pages (default 20, max 100) and max_depth (default 2, max 3); include/exclude filter paths by prefix (* suffix on include). Prefer readfetch_batch for a fixed URL list; readfetch_map to list URLs without fetching bodies; readfetch_text for a single page.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/crawl
  • readfetch_feedbackFREE — report integration, docs or site issues for a prior call.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    FREE — report integration, docs or site issues for a prior call. Bind with request_id from X-Request-Id. Paid delivery disputes use /v1/claims, not this tool.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: false
    • title: /v1/feedback
  • readfetch_mapPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Discover a site's crawlable surface without crawling it: parse robots.txt allow/disallow rules, collect URLs from sitemap.xml and sitemap indexes, find RSS, Atom and JSON feeds, and count internal and external links on the homepage. Use the returned URLs to plan readfetch_scrape, readfetch_batch, or readfetch_crawl — not readfetch_map again on each URL. Prefer readfetch_probe on one URL before paying for bodies.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/map
  • readfetch_pdfPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Extract text from a PDF (%PDF- magic, not Content-Type). Send exactly one of `url` (public http(s) link — egress GET, ≤ 20 MB) or `content_base64` (bytes you already have — the whole request body is capped at 1 MiB, base64 expansion included; optional `filename` labels the upload). Returns `pages` (per-page text), one concatenated `markdown` body, `title`, and `metadata`; $0.005 per document, not per page. `max_pages` limits extraction (default 50, max 200); documents over 200 pages or above your cap return 413 and are not billed. Scanned/image-only PDFs may return empty text with `billed: false` and a `hint`. Prefer readfetch_text or readfetch_scrape for HTML articles; readfetch_fetch for raw PDF bytes without extraction; readfetch_batch for many HTML URLs, not PDFs. Read-only server-side; paid x402 like other routes.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/pdf
  • readfetch_probeFREE — no payment or wallet: Free preflight on a URL before any paid readfetch_* call: HTTP status, content type, byte size, title, language, and whether a bot wall is waiting (`ch…Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    FREE — no payment or wallet: Free preflight on a URL before any paid readfetch_* call: HTTP status, content type, byte size, title, language, and whether a bot wall is waiting (`challenge`). When the response is HTML and not a challenge page, the JSON includes **`preview`**: the text readfetch_text would return (same extractor), up to **32,000 characters** for the first **3 probes per IP per day**, then **400 characters**. Use readfetch_probe instead of readfetch_text when choosing a route or estimating size; if `challenge: true`, use readfetch_scrape (then readfetch_residential if still blocked), not readfetch_text. Plain HTTP only — no browser render.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/probe
  • readfetch_residentialPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Identical request and response to /v1/scrape, but the render leaves through a residential address instead of the datacentre. For targets that block by IP reputation (DataDome, PerimeterX, Cloudflare, AWS WAF). One attempt, no retries: residential bandwidth is the cost, and four times the scrape price is what it takes to cover it honestly. Prefer readfetch_scrape when datacentre egress works; use readfetch_residential only after readfetch_scrape fails or readfetch_probe reports a persistent challenge.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/scrape/residential
  • readfetch_scrapePaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo 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.
    • untrusted-inputThe name "readfetch_scrape" says "scrape": 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.
    Description, as the server wrote it
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Load a public URL in headless Chromium and return Markdown, plain text, or HTML (`format`, plus status_code, title, billed; optional links via `advanced.include_links`). `mode` sets latency and depth: fast (15 s, minimal render), render (30 s, default, full JS), full (60 s, scroll the page). Put scroll, wait_for, js_code, headers, cookies, and auth in `advanced` (`options` is deprecated, same shape). Prefer readfetch_text when JavaScript is not required; readfetch_fetch for raw HTTP/API bytes; readfetch_residential when the site blocks datacentre IPs; readfetch_screenshot for a PNG/JPEG. Bot-check or empty extractions may return `billed: false` with a hint.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/scrape
  • readfetch_sectionPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Extract one heading or one CSS selector from a public page instead of the whole document. Returns matched Markdown or text, title, chars, content_sha256, and billed. If the heading is missing, returns HTTP 200 with empty text and `available_headings` so you can retry. `mode`: fast (plain HTTP) or render (default, Chromium when the page blocks HTTP). `max_chars` truncates output (default 8000, max 20000). Prefer readfetch_text for full articles; readfetch_scrape when content needs JavaScript.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/section
  • readfetch_textPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Fetch a public URL and return its main readable content as Markdown or plain text, plus title, author, published date and site name. Strips navigation, ads and boilerplate. No JavaScript rendering by default (cheaper than readfetch_scrape); one Chromium fallback when plain HTTP is blocked. Prefer readfetch_fetch when you need raw status, headers, or non-HTML bytes; readfetch_scrape when the article only appears after JavaScript runs.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/text
Only reads 5Show 5 read-only tools
  • readfetch_crawl_statusFREE — no payment or wallet: Poll a crawl job started with readfetch_crawl.Reads text others writeNo findings

    Why it is in this group

    • The name "readfetch_crawl_status" says "status": 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 "readfetch_crawl_status" says "crawl": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    Description, as the server wrote it
    FREE — no payment or wallet: Poll a crawl job started with readfetch_crawl. FREE — no payment or wallet; unauthenticated. Pass `id` from the crawl response. Returns job_id, status (queued, running, complete, or failed), completed/total counts, and a growing `pages` list (url plus Markdown) as results land. Stop polling when status is complete or failed. Results are kept for one hour after the job finishes.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/crawl/{id}
  • readfetch_diffPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "readfetch_diff" says "diff": 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 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
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Stateless change detection on readable page text (same HTTP-first extraction as readfetch_text): fetch the URL, compare to a hash or prior body you store client-side, return changed/unchanged plus optional line diff. First call with no prior fields returns a baseline hash (see hint). `previous_hash` alone detects change without a line diff; add `previous_content` when you need added/removed/diff. A no-change answer is still billable when text was delivered. Prefer readfetch_text when you need the full article once; readfetch_probe (free) for a short preview and `content_sha256` before spending on text.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/diff
  • readfetch_fetchPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "readfetch_fetch" says "fetch": 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 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
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Send an HTTP request (GET, POST, PUT, PATCH, DELETE, HEAD) through egress and return status_code, response headers, and body as text or base64 (`binary: true`). `max_bytes` caps the stored body; `follow_redirects` (default true) and `timeout_s` (95 s ceiling) apply to the full redirect chain. Use `json_body` for JSON POST/PUT payloads; use `body` for raw bytes or strings. Prefer readfetch_text for readable HTML articles; readfetch_pdf to extract PDF text (not raw bytes alone). POST/PUT/DELETE can change remote state despite readOnlyHint.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/fetch
  • readfetch_screenshotPaid routes require a funded Base USDC wallet.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "readfetch_screenshot" says "screenshot": 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 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
    Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Screenshot a public URL in headless Chromium (page JavaScript runs; no ad blocker) and return PNG or JPEG in JSON — `image_base64`, `mime`, `width`, `height`, `status_code`, `billed` (not a hosted URL). Scope: viewport only (`full_page: false`), full scrollable page (default), or one element (`selector`). `mode` caps total render time: fast (15 s), render (30 s, default), full (60 s, always full-page regardless of `full_page`). Set `width`/`height` before navigation (default 1280×800, max 3840×2160). `delay_ms` (0–30000) waits after navigation, then captures — raise it or use `mode=full` for slow SPAs and lazy media. Prefer readfetch_text or readfetch_scrape for extractable text; readfetch_pdf for PDF files; readfetch_fetch for raw HTTP without rendering. Read-only on the origin (GET + render, no form POST). Bot-check or blank frames may still return pixels with `billed: false` and a `hint`; paid x402 like other routes.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: /v1/screenshot

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 write14
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.

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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:19 UTC, unchanged since Nov 21, 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
10
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 10 tools that change things (10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://readfetch.com/mcp: tools/list returned 15 tools to an anonymous client, including readfetch_text (write), readfetch_map (write), readfetch_scrape (write), readfetch_residential (write), readfetch_batch (write) and 5 more

    What this check looks for

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 0.1.23. Values in angle brackets are yours to fill in.

claude mcp add --transport http x402-proxy https://readfetch.com/mcp
claude mcp add --transport http x402-proxy https://readfetch.com/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__x402-proxy__readfetch_search",
      "mcp__x402-proxy__readfetch_crawl_status"
    ],
    "ask": [
      "mcp__x402-proxy__readfetch_text",
      "mcp__x402-proxy__readfetch_map",
      "mcp__x402-proxy__readfetch_scrape",
      "mcp__x402-proxy__readfetch_residential",
      "mcp__x402-proxy__readfetch_fetch",
      "mcp__x402-proxy__readfetch_batch",
      "mcp__x402-proxy__readfetch_pdf",
      "mcp__x402-proxy__readfetch_section",
      "mcp__x402-proxy__readfetch_diff",
      "mcp__x402-proxy__readfetch_screenshot",
      "mcp__x402-proxy__readfetch_crawl",
      "mcp__x402-proxy__readfetch_probe",
      "mcp__x402-proxy__readfetch_feedback"
    ],
    "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 x402-proxy. Review it before you use it.

Capability tags behind 14 rules
  • mcp__x402-proxy__readfetch_text untrusted-input, outbound
  • mcp__x402-proxy__readfetch_map untrusted-input, outbound
  • mcp__x402-proxy__readfetch_scrape untrusted-input, outbound
  • mcp__x402-proxy__readfetch_residential untrusted-input, outbound
  • mcp__x402-proxy__readfetch_fetch untrusted-input, outbound
  • mcp__x402-proxy__readfetch_batch untrusted-input, outbound
  • mcp__x402-proxy__readfetch_pdf untrusted-input, outbound
  • mcp__x402-proxy__readfetch_section untrusted-input, outbound
  • mcp__x402-proxy__readfetch_diff untrusted-input, outbound
  • mcp__x402-proxy__readfetch_screenshot untrusted-input, outbound
  • mcp__x402-proxy__readfetch_search untrusted-input
  • mcp__x402-proxy__readfetch_crawl untrusted-input, outbound
  • mcp__x402-proxy__readfetch_crawl_status untrusted-input
  • mcp__x402-proxy__readfetch_probe 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/com.readfetch/mcp-x402-proxy/verify?hash=bceb6b02bb6a23c47a0621d76807b2f89ea8036ff75dbec39cd710d8847d7935" | jq -e '.changed == false'

Pinned hash bceb6b02bb6a, from Nov 21, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.readfetch/mcp-x402-proxy/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.readfetch/mcp-x402-proxy
[![Anlyon Radar](https://radar.anlyon.com/badge/com.readfetch/mcp-x402-proxy.svg)](https://radar.anlyon.com/servers/com.readfetch/mcp-x402-proxy)

Source: MCP Registry · repository. Synced Nov 21, 2026, 22:17 UTC.

readfetch MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the readfetch MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 10 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 readfetch MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the readfetch 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 readfetch MCP server have?

15 tools: 10 write, 5 read. readfetch_text, readfetch_map, readfetch_scrape, readfetch_residential, readfetch_batch, readfetch_pdf, readfetch_section, readfetch_crawl and 7 more.

Does the readfetch MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the readfetch MCP server send data to outside services?

12 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): readfetch_text, readfetch_map, readfetch_scrape, readfetch_residential, readfetch_fetch, readfetch_batch and 6 more.

Has the readfetch MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.