_ registry / mcp streamable-http · checked 10m ago

numetal-curb

https://api.curb.numetal.xyz

Registry code: 6042309a7ebf7500

api record

CURB clears peer-to-peer inference swaps. We accept payment in USDC on x402 on both Base and Solana, and via pay.sh on Solana. No upstream keys on the hub.

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

endpoint
https://api.curb.numetal.xyz/mcp
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 numetal-curb live?
Yes — it answered the hub's last check (checked 10m ago). It answered 39% of checks over the last 30 days.
Is numetal-curb free to use?
Yes — the hub reached it with no key and no payment.
What tools does numetal-curb have?
5 tools: swap_create_intent, swap_pay_challenge, swap_create_offer, swap_get_match, swap_list_offers.
Is numetal-curb 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
39.4%

90 days 23%· all time 23%

latency
409ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 87 checks · signed record
  • retired → live
  • down → retired· HTTP 500
  • degraded → down· HTTP 500
  • live → degraded· HTTP 500
  • down → live
_ what it is for
used for
  • buy llm inference from peer sellers
  • post an inference sell offer
  • list open inference offers
takes → gives
data → data
tools
3 reads2 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 5 tools
1 open 4 never probed 1 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.

  • swap_list_offers reads open 16h ago

    List open sell offers on CURB

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number"
        }
      }
    }
    arguments 8 lines
  • swap_create_intent changes data unknown never probed

    Post a buy intent; auto-matches an open offer when possible

    mcp-tool

    {
      "type": "object",
      "required": [
        "mtok"
      ],
      "properties": {
        "mtok": {
          "type": "number"
        },
        "buyer": {
          "type": "string"
        },
        "model": {
          "type": "string"
        },
        "offerId": {
          "type": "string"
        },
        "maxPriceUsd": {
          "type": "number"
        }
      }
    }
    arguments 23 lines
  • swap_pay_challenge reads unknown never probed

    Get the single-payee x402 challenge for a match (ONE gross accept per rail → the on-chain split; CURB fans out seller + hub fee on-chain)

    mcp-tool

    {
      "type": "object",
      "required": [
        "matchId"
      ],
      "properties": {
        "matchId": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • swap_create_offer changes data unknown never probed

    Post a sell offer (seller endpoint + payTo + model + mtok + priceUsd)

    mcp-tool

    {
      "type": "object",
      "required": [
        "sellerPayTo",
        "endpoint",
        "model",
        "mtok",
        "priceUsd"
      ],
      "properties": {
        "mtok": {
          "type": "number"
        },
        "note": {
          "type": "string"
        },
        "model": {
          "type": "string"
        },
        "endpoint": {
          "type": "string"
        },
        "priceUsd": {
          "type": "number"
        },
        "sellerPayTo": {
          "type": "string"
        }
      }
    }
    arguments 30 lines
  • swap_get_match reads unknown 16h ago

    Fetch a match (payment challenge + grant after pay)

    mcp-tool

    {
      "type": "object",
      "required": [
        "matchId"
      ],
      "properties": {
        "matchId": {
          "type": "string"
        }
      }
    }
    arguments 11 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 6042309a7ebf7500.

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

_ also on numetal.xyz 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.