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

x402-cluster

https://x402-cluster.ian-944.workers.dev

Registry code: 46f4221c22bb8546

api record

Zero-signup web scraping, HTML-to-JSON extraction & compliance checks on Base L2 ($0.01 USDC/call).

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

endpoint
https://x402-cluster.ian-944.workers.dev/v1/mcp.json
protocol
streamable-http ·2024-11-05
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-cluster live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is x402-cluster free to use?
Yes — the hub reached it with no key and no payment.
What tools does x402-cluster have?
6 tools: preview_extract, extract_dynamic_url, extract_structured_data, parse_web_schema, validate_compliance, extract_from_url.
Is x402-cluster 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
542ms

last good check

priced tools
0

of 6 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. 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: 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 6 tools
6 never probed 0 of 6 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.

  • preview_extract unknown never probed

    FREE trial of extract_structured_data. Limited to 5 calls per hour per IP. Truncates raw_text to 500 characters. No payment required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "raw_text"
      ],
      "properties": {
        "raw_text": {
          "type": "string",
          "maxLength": 500,
          "description": "Text to extract from."
        },
        "target_schema": {
          "type": "object",
          "description": "JSON schema to extract."
        }
      }
    }
    arguments 17 lines
  • extract_dynamic_url unknown never probed

    Render a JavaScript-heavy webpage (React, Next.js, Vue, dynamic pricing tables, SPAs) in headless Chromium on Cloudflare's edge, wait for client-side hydration, and return strict typed JSON matching target_schema ($0.05/call or 5 prepaid credits).

    mcp-tool

    {
      "type": "object",
      "required": [
        "url",
        "target_schema"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "Public HTTP or HTTPS URL requiring full JavaScript browser rendering."
        },
        "wait_ms": {
          "type": "number",
          "description": "Optional extra delay in milliseconds (0-3000) after network idle for late client renders."
        },
        "target_schema": {
          "type": "object",
          "description": "JSON object defining desired output keys and expected types."
        }
      }
    }
    arguments 22 lines
  • extract_structured_data unknown 13h ago

    Convert raw text, email bodies, receipts, logs, or HTML snippets already in memory into strict typed JSON conforming to target_schema. Use when you already have the source text and need deterministic schema enforcement without burning local reasoning tokens. Strictly capped at 6,000 bytes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "raw_text"
      ],
      "properties": {
        "raw_text": {
          "type": "string",
          "maxLength": 6000,
          "description": "Unstructured text, HTML fragment, or document snippet to normalize (max 6,000 bytes)."
        },
        "target_schema": {
          "type": "object",
          "description": "Declarative key-type map defining the exact JSON structure to return."
        }
      }
    }
    arguments 17 lines
  • parse_web_schema unknown 13h ago

    Fast key-value entity extraction from raw web or document text when you only need a flat list of named fields rather than a full nested JSON Schema. Ideal for pulling contacts, dates, tickers, or metadata out of messy text (max 6,000 bytes).

    mcp-tool

    {
      "type": "object",
      "required": [
        "content",
        "fields"
      ],
      "properties": {
        "fields": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "minItems": 1,
          "description": "Exact entity or field names to extract as keys."
        },
        "content": {
          "type": "string",
          "maxLength": 6000,
          "description": "Raw web or document text to scan (max 6,000 bytes)."
        }
      }
    }
    arguments 22 lines
  • validate_compliance unknown never probed

    Audit a JSON payload against regulatory, PII, or business policy rules before executing downstream transactions or API writes. Returns pass/fail status and specific rule violations (e.g., PII exposure, OFAC/KYC checks, field bounds).

    mcp-tool

    {
      "type": "object",
      "required": [
        "payload"
      ],
      "properties": {
        "rules": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Natural-language or policy rules the payload must satisfy."
        },
        "payload": {
          "type": "object",
          "description": "Structured JSON object to audit against compliance rules."
        }
      }
    }
    arguments 19 lines
  • extract_from_url unknown 13h ago

    Fetch a public static webpage URL, strip HTML/navigation boilerplate, and return strict typed JSON matching target_schema in one atomic step ($0.01/call). Best for static HTML pages, docs, and articles. For React/Next.js/Vue SPAs, use extract_dynamic_url.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url",
        "target_schema"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "Public HTTP or HTTPS webpage URL to fetch and parse."
        },
        "target_schema": {
          "type": "object",
          "description": "JSON object defining desired output keys and expected types."
        }
      }
    }
    arguments 18 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 46f4221c22bb8546.

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