RailFi Payout Plans
by railfi.xyz in Other
Free, non-custodial tools to validate bounded USDC/USDT payout plans and reconcile payouts.
https://railfi.xyz/api/mcp- Tools
- 4
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 286 ms
- 342 ms slowest 5%
- Last check
- Passed
- 7 h ago, next any minute now
Scan it nowHow to connectCompare alternatives from other providers
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"railfi-payout-plans": {
"type": "http",
"url": "https://railfi.xyz/api/mcp"
}
}
}4 tools
- create_payout_plan
Validate a bounded stablecoin payout run (recipients, budget, time window) and return an approve-once pack the OWNER approves in their own wallet. RailFi never holds funds or keys and does not execute payments.
- validate_payout_plan
Check a payout plan for bad addresses, bad amounts, duplicates, inverted window and over-budget totals.
- reconcile_payouts
Match on-chain transfer records (recipient, amount, txHash) to plan lines and report which invoices are paid, unpaid, or unexpected transfers.
- fetch_transfers
Read-only: look up public USDC/USDT Transfer events to the given recipients (optionally from one payer) over up to 10000 recent blocks via a public RPC. Output plugs straight into reconcile_payouts. No keys, no signing.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 7 h ago | Passed | 200 | 286 ms |
| 18 h ago | Passed | 200 | 286 ms |
| 27 h ago | Passed | 200 | 293 ms |
| 38 h ago | Passed | 200 | 256 ms |
| 47 h ago | Passed | 200 | 300 ms |
Show 1 older checks
| 2 days ago | Passed | 200 | 342 ms |