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

base-usdc-payment-verifier

https://x402-usdc-verify.onrender.com

Registry code: d7dca86e62dbca6f

api record

Call verify_usdc_payment to check a Base / Base Sepolia tx is a confirmed native-USDC transfer. It costs 0.01 USD in USDC via x402 on eip155:8453: an unpaid call returns isError + PaymentRequired; retry with params._meta["x402/payment"]. get_pricing is free.

endpoint
https://x402-usdc-verify.onrender.com/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 base-usdc-payment-verifier live?
Partly — its last checks failed now and then (checked 2h ago). It answered 50% of checks over the last 30 days.
Is base-usdc-payment-verifier free to use?
Yes — the hub reached it with no key and no payment.
What tools does base-usdc-payment-verifier have?
2 tools: verify_usdc_payment, get_pricing.
Is base-usdc-payment-verifier 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
degraded
uptime, 30 days
50%

90 days 50%· all time 50%

latency
233ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 2 checks · signed record
  • live → degraded· HTTP 503
  • 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 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
1

distinct

settlements
1

last 2026-10-29

received on chain
0.1 USDC

counted from three payers (thin, concentrated, shared-payto)

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

  • get_pricing open 26h ago

    Free. Returns the x402 price, network, USDC asset, payTo address and facilitator for the paid verify_usdc_payment tool.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • verify_usdc_payment unknown never probed

    Verify a Base (mainnet, default) or Base Sepolia transaction is a successful, confirmed transfer of native Circle USDC (not a look-alike token) to an expected recipient for an exact or minimum amount. Checks receipt status, canonical block, confirmations, optional payer, notBefore/maxAge windows; returns verdict valid|invalid|pending|not_found with machine-readable reasons and the matched Transfer log. Not charged on 4xx/5xx errors. PAID: 0.01 USD in USDC per successful call via x402 (eip155:8453). Malformed input is rejected before payment.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "txHash",
        "expectedTo"
      ],
      "properties": {
        "chain": {
          "enum": [
            "base",
            "base-sepolia"
          ],
          "type": "string",
          "description": "Chain of the tx being verified (default base)"
        },
        "txHash": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{64}$",
          "description": "0x-prefixed 32-byte transaction hash"
        },
        "notBefore": {
          "type": "integer",
          "description": "Unix seconds; reject txs mined earlier (anti-replay)"
        },
        "expectedTo": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "Recipient that must receive USDC"
        },
        "amountMatch": {
          "enum": [
            "exact",
            "atLeast"
          ],
          "type": "string",
          "description": "exact (default) or atLeast"
        },
        "expectedFrom": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "Optional required payer"
        },
        "maxAgeSeconds": {
          "type": "integer",
          "description": "Reject txs older than this many seconds"
        },
        "expectedAmount": {
          "type": "string",
          "description": "Decimal USDC, max 6 decimals, e.g. \"0.10\" (or expectedAmountAtomic)"
        },
        "minConfirmations": {
          "type": "integer",
          "maximum": 10000,
          "minimum": 1,
          "description": "Default 3"
        },
        "expectedAmountAtomic": {
          "type": "string",
          "description": "Integer atomic units (1 USDC = 1000000)"
        }
      },
      "additionalProperties": false
    }
    arguments 64 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 d7dca86e62dbca6f.

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