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

payments-intel

https://payments-intel-production.up.railway.app

Registry code: 6a56b85ebc9726a2

api record

Cited data on stablecoin rails, on/off-ramps, corridors and payment providers. search_providers is free; other tools are paid per call via x402/MPP (you pay). Every fact carries source URL, date and confidence. Information, not financial advice.

endpoint
https://payments-intel-production.up.railway.app/mcp
protocol
streamable-http ·2025-03-26
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 payments-intel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is payments-intel free to use?
Yes — the hub reached it with no key and no payment.
What tools does payments-intel have?
4 tools: search_providers, find_corridor, get_provider, stablecoin_rails.
Is payments-intel 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
633ms

last good check

priced tools
1

of 4 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

_ what it can do 4 tools
1 paid3 open 4 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.

  • stablecoin_rails 0.01 USDC paid never probed

    Who can on-ramp, off-ramp, issue or settle this stablecoin, on which chain, in which country? Paid ($0.01 USDC): Stablecoin rails by asset, chain, country and service, with the cited stablecoin block for each matching provider (assets, chains, ramp countries, fiat rails, custody model). Country matches say whether the country is listed or only covered by a 'global' claim. This server holds no wallet and never pays: it returns the HTTP 402 payment requirements (x402 on Base, MPP on Tempo) and the URL https://payments-intel-production.up.railway.app/v1/stablecoin-rails. Pay with your own x402/MPP client and retry that URL.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "asset": {
          "type": "string",
          "description": "Stablecoin ticker, e.g. USDC, EURC, USDT, PYUSD"
        },
        "chain": {
          "type": "string",
          "description": "Chain, e.g. base, ethereum, solana, tron, polygon"
        },
        "country": {
          "type": "string",
          "description": "ISO 3166-1 alpha-2 country for on/off-ramp coverage, e.g. MX"
        },
        "service": {
          "type": "string",
          "description": "issuance, mint_redeem, on_ramp, off_ramp, payouts, acceptance, settlement, custody, wallets, orchestration, fx, cards"
        }
      }
    }
    arguments 22 lines
  • search_providers open 1h ago

    Which payment or stablecoin providers support this asset, chain, country or service? Free: search payment and stablecoin providers by category, asset, chain, ramp country or service. Returns compact cards (no citations); use get_provider for the full cited record. 50 calls/day per client.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "q": {
          "type": "string",
          "description": "Name search, e.g. 'bridge'"
        },
        "asset": {
          "type": "string",
          "description": "Stablecoin ticker, e.g. USDC, EURC, USDT, PYUSD"
        },
        "chain": {
          "type": "string",
          "description": "Chain, e.g. base, ethereum, solana, tron, polygon"
        },
        "country": {
          "type": "string",
          "description": "ISO 3166-1 alpha-2 country for on/off-ramp coverage, e.g. MX"
        },
        "service": {
          "type": "string",
          "description": "issuance, mint_redeem, on_ramp, off_ramp, payouts, acceptance, settlement, custody, wallets, orchestration, fx, cards"
        },
        "category": {
          "type": "string",
          "description": "card_acquiring, orchestration, merchant_of_record, payouts, fx, baas_issuing, open_banking, stablecoin_issuer, stablecoin_infra, onoff_ramp, custody_wallets, agentic_payments"
        }
      }
    }
    arguments 30 lines
  • find_corridor open 1h ago

    Who can move money from this currency or stablecoin to that one, in this country, over which rails? Paid ($0.03 USDC): Money-movement routes from one currency or stablecoin to another: corridors providers publish (rails, speed, fee notes, cited), plus on/off-ramp routes inferred from ramp coverage, labelled as inferred. This server holds no wallet and never pays: it returns the HTTP 402 payment requirements (x402 on Base, MPP on Tempo) and the URL https://payments-intel-production.up.railway.app/v1/corridor. Pay with your own x402/MPP client and retry that URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Currency or stablecoin received, e.g. MXN"
        },
        "from": {
          "type": "string",
          "description": "Currency or stablecoin sent, e.g. USDC or USD"
        },
        "country": {
          "type": "string",
          "description": "Destination ISO alpha-2 country, e.g. MX"
        }
      }
    }
    arguments 21 lines
  • get_provider open 1h ago

    What exactly does this provider support, where is it licensed and what does it charge? Paid ($0.01 USDC): Full cited record for one provider: stablecoin rails, corridors, licences, published fees, coverage, developer and agent-payment support. Every fact has source URL, retrieval date, quote and confidence. This server holds no wallet and never pays: it returns the HTTP 402 payment requirements (x402 on Base, MPP on Tempo) and the URL https://payments-intel-production.up.railway.app/v1/provider. Pay with your own x402/MPP client and retry that URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Provider id from search_providers, e.g. circle"
        }
      }
    }
    arguments 12 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 6a56b85ebc9726a2.

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