_ registry / mcp streamable-http · checked 59m ago

gofetch

https://getgofetch.dev

Registry code: 5899417bf486d908

api record

gofetch turns one public web page into JSON fields (gofetch_extract, $0.01, charged only when ok). Payment is x402 v2, USDC on Base. Call gofetch_pricing (free) first. If your client cannot attach an x402 payment, gofetch_extract returns the PaymentRequired object and the HTTP route to call with an x402 wallet tool (AgentCash, MetaMask Agent Wallet, Coinbase Payments MCP). Static HTML only: no JavaScript rendering, no paywall or login bypass. JS-rendered or bot-protected sites return ok:false with error needs_js or blocked and are not charged. Guide: https://getgofetch.dev/agents

endpoint
https://getgofetch.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
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 gofetch live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is gofetch free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does gofetch have?
2 tools: gofetch_pricing, gofetch_extract.
Is gofetch 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
149ms

last good check

priced tools
1

of 2 tools

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

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 3 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
4

last 2026-10-24

received on chain
0.03 USDC

counted from three payers (thin, concentrated)

_ what it can do 2 tools
1 paid1 open 2 of 2 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.

  • gofetch_extract 0.01 USDC paid 59m ago

    Reads static HTML only: it does not run JavaScript, so JS-rendered sites (most big retailers) and bot-protected sites fail with ok:false, error needs_js or blocked, and no charge. Paid: $0.01 USDC on Base via x402, charged only when ok is true. Returns the fields described by a JSON Schema (up to 20 properties) from one public page. Without an x402 payment in _meta["x402/payment"] it returns the price and how to pay instead.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url",
    "schema"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "description": "Public http(s) page URL"
    },
    "schema": {
      "type": "object",
      "description": "JSON Schema of the fields to return (max 20 properties)"
    }
  }
}
    arguments 18 lines
  • gofetch_pricing open 59m ago

    Free. Returns gofetch's paid routes, prices, payTo, network, facilitator and the ways an agent can pay (x402 v2, USDC on Base). Call this first.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
_ try it 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 5899417bf486d908.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5899417bf486d908/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/5899417bf486d908/badge.svg)](https://brick.blue/agent/5899417bf486d908?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 know
card completeness
60%

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.