_ registry / mcp streamable-http · checked 2h ago

x402-web-extract

https://x402-web-extract.senpi-agent.workers.dev

Registry code: 42ddfb5346568d44

api record

Pay-per-use web extract, token prices, and wallet balances via x402 USDC micropayments.

from a public catalogue that lists it, not from the operator

endpoint
https://x402-web-extract.senpi-agent.workers.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 x402-web-extract live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is x402-web-extract free to use?
Yes — the hub reached it with no key and no payment.
What tools does x402-web-extract have?
5 tools: fetch_url, token_price, wallet_balance, youtube_video, youtube_audio.
Is x402-web-extract 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 99.7%· all time 99.7%

latency
462ms

last good check

priced tools
2

of 5 tools

_ answered our checks, 90 days 394 checks · signed record
  • degraded → live
_ what it is for
topic
search & web scraping & fetch
used for
  • fetch a url as markdown
  • get token spot price
  • get wallet balance
  • get a video download url
  • get an audio stream url
takes → gives
text → text, data
tools
5 reads
_ 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 also stands behind 1 other origin: the chain figures are the gateway's, not this listing's alone. 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
10

distinct

settlements
13

last 2026-11-01

received on chain
0.13 USDC

shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
2 paid 3 never probed 2 of 5 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.

  • youtube_video reads 1 USDC paid never probed

    Resolve any YouTube video URL (watch?v=, youtu.be, shorts, embed) to a direct MP4 download URL with title, uploader, and format metadata. Provide url (http/https). Costs 1.00 USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • youtube_audio reads 0.5 USDC paid never probed

    Resolve any YouTube video URL to its audio-only stream download URL (m4a/webm when available) with title, uploader, and format metadata. Provide url (http/https). Costs 0.50 USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • fetch_url reads unknown 25h ago

    Fetch any public URL and return a clean, readable markdown or JSON extract for AI agents. Pass the target as url (http/https). Costs 0.01 USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • token_price reads unknown never probed

    Real-time USDC-denominated spot price for an EVM token by contract address or common symbol. Provide address (0x...) or symbol (ETH, USDC, USDT, WETH) and optional chain (base, ethereum, polygon, arbitrum, optimism, avalanche, default base). Costs 0.01 USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "chain": {
      "type": "string"
    },
    "symbol": {
      "type": "string"
    },
    "address": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • wallet_balance reads unknown never probed

    Query the native and USDC balance for any EVM wallet address. Provide address (0x...) and optional chain (base, ethereum, polygon, arbitrum, optimism, default base). Costs 0.02 USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "chain": {
      "type": "string"
    },
    "address": {
      "type": "string"
    }
  }
}
    arguments 15 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 42ddfb5346568d44.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/42ddfb5346568d44/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/42ddfb5346568d44/badge.svg)](https://brick.blue/agent/42ddfb5346568d44?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
90%

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
1
ok
0
failed
0
success rate
0%
median latency
392ms
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
—

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