RailFi Payout Plans MCP server
online · 100% uptimexyz.railfi/payout-plans·v0.1.0Free, non-custodial tools to validate bounded USDC/USDT payout plans and reconcile payouts.
0 stars
Reviews
Write oneNobody has reviewed RailFi Payout Plans yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
RailFi Payout Plans tools (3, 1 write)
write = sends, deletes, buys or postscreate_payout_planwrite actionFreeValidate 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.
reconcile_payoutsFreeMatch on-chain transfer records (recipient, amount, txHash) to plan lines and report which invoices are paid, unpaid, or unexpected transfers.
validate_payout_planFreeCheck a payout plan for bad addresses, bad amounts, duplicates, inverted window and over-budget totals.
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 621ms20/20
- Tool poisoning3 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How RailFi Payout Plans compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 81/100
- higher than 62% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 345 ms
- faster than 42% of 30,031 servers
What its tools let an agent do: 2 read · 1 create
Install RailFi Payout Plans in Claude Code, Cursor or VS Code
claude mcp add --transport http payout-plans https://railfi.xyz/api/mcp
What the publisher says
From the RailFi Payout Plans repository's README, as published. We do not edit it. Read it on GitHub
RailFi 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
Tools
Install / connect (remote)
Point any MCP client that supports remote streamable HTTP at:
https://railfi.xyz/api/mcpNo 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/send is not implemented.
- Software only — not a money transmitter, bank, or custodian. No token. No tax/legal/investment advice.
Contact
info@railfi.xyz · https://railfi.xyz
Nothing above is checked by us. What we check is on the safety report.
RailFi Payout Plans: common questions
- Is RailFi Payout Plans MCP server safe?
- Mostly: it is graded B (81/100). Read the RailFi Payout Plans safety report
- How do I install RailFi Payout Plans?
- It runs remotely at railfi.xyz. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does RailFi Payout Plans need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is RailFi Payout Plans maintained?
- The last commit was 21 days ago (2026-10-14). The latest release is v0.1.0.
- Is RailFi Payout Plans up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does RailFi Payout Plans compare with other MCP servers?
- safety score 81/100 (higher than 62% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.