_ registry / mcp + a2a HTTP+JSON · checked 3h ago

readfetch.com

https://readfetch.com

Registry code: 8aaaeccaaa54a253

api record

REST endpoints as tools. An unpaid tool call returns 402 with the x402 accepts block in structuredContent; retry the same call with PAYMENT-SIGNATURE.

endpoint
https://readfetch.com/
door code
c7462e6a35296f7b
protocol
HTTP+JSON ·1.0
authentication
http
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is readfetch.com live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is readfetch.com free to use?
Yes — the hub reached it with no key and no payment.
What tools does readfetch.com have?
13 tools: probe, scrape, diff, screenshot, search, map, residential, fetch, ….
Is readfetch.com safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
282ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes

_ what it can do 13 tools
13 auth-required 13 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • probe auth-required never probed

    Metadata before spending: status, content type, size, title, language and whether a bot wall is waiting. No page body, no browser, always free.

    probemetadatapreflightcontent typebot detection

  • scrape auth-required never probed

    JavaScript rendering and web scraping for agents: load a public URL in a real browser session, optionally scroll, wait for selectors, run JS, set headers, cookies or auth, and return Markdown, text or HTML with the page's links.

    scrapejavascript renderingbrowser renderingmarkdownhtmlspaweb scraping

  • diff auth-required never probed

    Stateless change detection: send the hash you hold, get changed/unchanged and a bounded diff. A no-change answer is billable.

    diffchange detectionhashmonitoringstateless

  • screenshot auth-required never probed

    PNG or JPEG of a rendered page: viewport, full page, or one element.

    screenshotpngjpegfull pageelement

  • search auth-required never probed

    Web search without a search subscription, returning titles, URLs and snippets.

    searchweb searchserpresultssnippets

  • map auth-required never probed

    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 a /v1/scrape or /v1/crawl.

    sitemaprobots.txtrssatomfeed discoveryurl discoverysite mapcrawl planninglink inventory

  • scrape-residential auth-required never probed

    Identical request and response to /v1/scrape, but the render leaves through a rotating 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.

    residential proxyprotected sitesanti-botscrapebrowser rendering

  • fetch auth-required never probed

    Send an arbitrary HTTP request (GET, POST, PUT, PATCH, DELETE, HEAD) and return the response with status, headers and body, as text or base64. Intended for APIs, GraphQL, PDFs, byte ranges and large payloads where a browser is not needed.

    http clientraw httpapi callsgraphqlproxy

  • batch auth-required never probed

    Up to 50 URLs in one call and one payment. Results in input order; an undelivered page is not billed and is credited.

    batchbulkmultiple urlsconcurrentmarkdown

  • pdf auth-required never probed

    Documents, not pages: page text plus one Markdown body, priced per document.

    pdfdocument textpage textmarkdownmetadata

  • section auth-required never probed

    One heading or one selector instead of the whole page. A heading that is not found returns 200, an empty body and the list of headings that do exist.

    sectionheadingselectortokensdocs

  • crawl auth-required never probed

    Bounded async crawl with a job id, a page cap quoted up front, and per-page Markdown.

    crawlsiteasyncjobmarkdown

  • text auth-required never probed

    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, so it costs a fraction of a browser scrape; use /v1/scrape when the content only appears after JavaScript runs.

    readabilityarticle extractionhtml to texthtml to markdownweb readercontent extractionmetadataopen graphno javascript

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8aaaeccaaa54a253.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8aaaeccaaa54a253/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8aaaeccaaa54a253/badge.svg)](https://brick.blue/agent/8aaaeccaaa54a253?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.