About RailFi Payout Plans
RailFi Payout Plans is an MCP server for teams and agents to validate stablecoin payout plans and reconcile transfers. It creates bounded drafts for approval in the owner's wallet; it never holds funds or keys or executes payments.
Key features
- 01Validate recipients, amounts, budgets, and time windows
- 02Create payout packs for wallet approval
- 03Look up public USDC/USDT transfers read-only
- 04Reconcile transfers and report payout progress
Use cases
- 01Check invoice payout rows and budgets before approval
- 02Prepare a draft for one-time approval in the owner's wallet
- 03Look up transfers on Polygon, Base, Ethereum, or Arbitrum
- 04Match landed transfers to payout lines and track progress
MCP support
The MCP server exposes payout-plan creation and validation, transfer lookup, and reconciliation tools over streamable HTTP. It does not custody funds or keys, or execute payments.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://railfi.xyz/api/mcpclaude mcp add --transport http xyz-railfi-payout-plans https://railfi.xyz/api/mcp{"mcpServers":{"xyz-railfi-payout-plans":{"type":"http","url":"https://railfi.xyz/api/mcp"}}}Open in Cursor{"servers":{"xyz-railfi-payout-plans":{"type":"http","url":"https://railfi.xyz/api/mcp"}}}Open in VS Code{"mcpServers":{"xyz-railfi-payout-plans":{"type":"http","url":"https://railfi.xyz/api/mcp"}}}{"mcpServers":{"xyz-railfi-payout-plans":{"serverUrl":"https://railfi.xyz/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
4| Parameter | Type | Required | Description |
|---|---|---|---|
| csv | string | No | Optional CSV: invoice_ref,recipient,amount[,note] |
| name | string | Yes | |
| lines | array | No | |
| token | enum | Yes | USDC | USDT |
| budget | string | Yes | Max total in token units, e.g. "1000" |
| network | enum | Yes | polygon | base | ethereum | arbitrum |
| windowEnd | string | Yes | ISO 8601 |
| windowStart | string | Yes | ISO 8601 |
Details
From the project READMERailFi MCP
Free, non-custodial MCP server for agent-safe stablecoin payout plans.
RailFi helps teams (and agents) turn invoice/payout rows into a bounded payout-run draft the owner approves once in their own wallet. Tools validate plans and reconcile transfers; they never hold funds or keys and do not execute payments.
Endpoints
| What | URL |
|---|---|
MCP (streamable HTTP, JSON-RPC, protocol 2025-06-18) | https://railfi.xyz/api/mcp |
| A2A agent card | https://railfi.xyz/.well-known/agent-card.json |
| Web app (plans) | https://railfi.xyz/plans?src=site |
| Early-bird beta | https://railfi.xyz/beta?src=site |
Tools
| Tool | Use when |
|---|---|
create_payout_plan | You need to validate recipients, amounts, total budget and time window, then export an approve-once pack for the owner's wallet |
validate_payout_plan | You want to check a plan without creating an export |
fetch_transfers | Read-only public USDC/USDT Transfer lookup (Polygon, Base, Ethereum, Arbitrum) |
reconcile_payouts | Transfers landed and you need to mark lines paid (tx hash) or skipped and report progress |
Install / connect (remote)
{ "mcpServers": { "railfi": { "type": "streamable-http", "url": "https://railfi.xyz/api/mcp" } } }
No API key. No OAuth. Rate limit: 60 requests/min/IP.
Honesty
- Non-custodial: you sign in your own wallet; RailFi never holds private keys or balances.
- A2A
message/sendis not implemented. - Software only — not a money transmitter, bank, or custodian.
Contact
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.