Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Stablecoin rails, corridors and payment provider data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Stablecoin on/off-ramps, corridors and payment providers by country, with cited data. x402/MPP paid.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http stablecoin-rails-corridors-and-payment-provid-mcp https://payments-intel-production.up.railway.app/mcp
# 2 — ask your agent for something these tools do
# search_providers, get_provider, stablecoin_rails and 5 more
Stablecoin rails, corridors and payment provider data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http stablecoin-rails-corridors-and-payment-provid-mcp https://payments-intel-production.up.railway.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | card_acquiring, orchestration, merchant_of_record, payouts, fx, baas_issuing, open_banking, stablecoin_issuer, stablecoin_infra, onoff_ramp, custody_wallets, agentic_payments |
| q | string | no | Name search, e.g. 'bridge' |
| asset | string | no | Stablecoin ticker, e.g. USDC, EURC, USDT, PYUSD |
| chain | string | no | Chain, e.g. base, ethereum, solana, tron, polygon |
| country | string | no | ISO 3166-1 alpha-2 country for on/off-ramp coverage, e.g. MX |
| service | string | no | issuance, mint_redeem, on_ramp, off_ramp, payouts, acceptance, settlement, custody, wallets, orchestration, fx, cards |
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 (x
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Provider id from search_providers, e.g. circle |
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 wall
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | no | Stablecoin ticker, e.g. USDC, EURC, USDT, PYUSD |
| chain | string | no | Chain, e.g. base, ethereum, solana, tron, polygon |
| country | string | no | ISO 3166-1 alpha-2 country for on/off-ramp coverage, e.g. MX |
| service | string | no | issuance, mint_redeem, on_ramp, off_ramp, payouts, acceptance, settlement, custody, wallets, orchestration, fx, cards |
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 re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Currency or stablecoin sent, e.g. USDC or USD |
| to | string | yes | Currency or stablecoin received, e.g. MXN |
| country | string | no | Destination ISO alpha-2 country, e.g. MX |
What do the paid endpoints return, and what do they cost? Free: prices and paths of every paid endpoint, plus a full example response for GET /v1/provider taken verbatim from a real record, labelled as an example with its last-verified date. Use it to see the shape and depth of paid data before paying.
No parameter schema on file.
Is this address well formed for this chain, and what is its EIP-55 checksummed form? Free: deterministic address format check for EVM chains (EIP-55 checksum: valid, checksummed form, whether the input checksum was correct, all lowercase or all uppercase) and Solana (base58, 32 bytes). No external calls. 60 calls/min per client. Format only; says nothing about who controls an address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | Chain id or name: an EVM chain (e.g. base, ethereum, eip155:8453) or solana |
| address | string | yes | Address to check |
What are the basic facts of this chain (CAIP-2 id, gas token, explorer, x402/MPP settlement, stablecoins)? Paid ($0.001 USDC): Cited chain facts from a prepared dataset: CAIP-2 chain id, gas token, finality class, block explorer, whether x402 and MPP settle there, and stablecoins. Fields not established from a source are the string "unknown". Unknown chains and malformed input return 404/400 and a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | Chain slug, name or CAIP-2 id, e.g. base, solana, eip155:8453 |
What are the symbol, name, decimals, contract address and issuer of this stablecoin on this chain? Paid ($0.001 USDC): Cited stablecoin token facts from a prepared dataset (USDC, EURC, USDT, PYUSD, DAI on the chains /v1/chain covers, where a permissively licensed source lists them): symbol, name, decimals, contract address, chain, issuer, each with a source citation and license. Fields not establi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | Chain slug, name or CAIP-2 id, e.g. base, solana, eip155:8453 |
| symbol | string | no | Stablecoin ticker, e.g. USDC (give symbol or address) |
| address | string | no | Token contract / mint address (give address or symbol) |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Stablecoin rails, corridors and payment provider data or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Stablecoin rails, corridors and payment provider data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.