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

x402-life

https://x402.life

Registry code: 24091d07d15a0c36

api record

Quote before payment. A staged payment is not settled. Final Solana authorization must follow the host application's confirmation and signing policy.

endpoint
https://x402.life/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
0 · newcomer
_ is it live, free and safe measured by this hub
Is x402-life live?
No — it has stopped answering the hub's checks (checked 23m ago). It answered 89% of checks over the last 30 days.
Is x402-life free to use?
Not measured yet.
What tools does x402-life have?
2 tools: x402_stage_payment, x402_get_payment_quote.
Is x402-life 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
down
uptime, 30 days
88.5%

90 days 93.4%· all time 93.4%

latency
4,299ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 349 checks · signed record
  • degraded → down· HTTP 402: vercel DEPLOYMENT_DISABLED
  • live → degraded· HTTP 402: vercel DEPLOYMENT_DISABLED
  • degraded → live
  • live → degraded· HTTP 500: vercel INTERNAL_FUNCTION_INVOCATION_FAILED
  • degraded → live
_ what it is for
topic
payments & commerce payment infrastructure
used for
  • quote an x402 payment on solana
  • stage a payment for user review
takes → gives
data → data
tools
1 reads1 changes data
_ 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

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

  • x402_stage_payment changes data unknown never probed

    Stage a previously quoted x402 payment for user review. Does not sign or broadcast the Solana transaction.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "quoteId"
  ],
  "properties": {
    "quoteId": {
      "type": "string",
      "maxLength": 128,
      "minLength": 1
    }
  }
}
    arguments 14 lines
  • x402_get_payment_quote reads unknown never probed

    Quote an x402 service payment settling on Solana without executing payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "service"
  ],
  "properties": {
    "units": {
      "type": "integer",
      "maximum": 1000000,
      "minimum": 1
    },
    "service": {
      "type": "string",
      "maxLength": 160,
      "minLength": 1
    },
    "currency": {
      "enum": [
        "USDC",
        "SOL"
      ],
      "type": "string"
    },
    "maxAmountUsd": {
      "type": "number",
      "maximum": 1000000,
      "minimum": 0
    }
  }
}
    arguments 31 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 24091d07d15a0c36.

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