_ registry / mcp http-sse · checked 5m ago

x402-web-tools

https://x402-web-tools.onrender.com

Registry code: 9a873bc8bc155c8c

api record

Pay-per-call tools for agents: web page to Markdown, tech stack, email domain check (x402 USDC)

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

endpoint
https://x402-web-tools.onrender.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is x402-web-tools live?
Yes — it answered the hub's last check (checked 5m ago). It answered 100% of checks over the last 30 days.
Is x402-web-tools free to use?
Not measured yet.
What tools does x402-web-tools have?
4 tools: extract_webpage, detect_tech_stack, check_email_domain, pricing.
Is x402-web-tools 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
99.6%

90 days 99.5%· all time 99.5%

latency
880ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 377 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check email domain records
  • detect website technology stack
  • extract web page content
  • get tool pricing
takes → gives
text, web pages → data, text
tools
4 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 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
3

distinct

settlements
4

last 2026-11-10

received on chain
0.008 USDC

no flags

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • extract_webpage reads unknown never probed

    Fetch any public web page and return clean readable Markdown (Readability), title, description, og:image, byline, word count and outgoing links. Ideal for LLM agents that need page content without HTML noise. Costs $0.003 USDC (x402, Base).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "Public http(s) URL"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • detect_tech_stack reads unknown never probed

    Detect the technology stack of a website: frameworks (Next.js, React, Vue, Angular...), CMS (WordPress, Shopify, Webflow...), analytics, payments, CDN/hosting and server headers. Useful for lead qualification and competitor research. Costs $0.003 USDC (x402, Base).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "Public http(s) URL"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • check_email_domain reads unknown never probed

    Check an email address or domain: MX records, mail provider (Google/Microsoft/Zoho), SPF, DMARC policy, disposable-domain flag and a 0-100 deliverability score. Validate leads before sending. Costs $0.002 USDC (x402, Base).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Domain or full email address"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • pricing reads unknown never probed

    Free. Lists tools, prices and payment details of this server.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    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 9a873bc8bc155c8c.

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

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.