RailFi Payout Plans
MCP server by RailFi
Validate bounded USDC and USDT payout plans, look up public transfers and reconcile payouts without holding funds or keys.
Connect to RailFi Payout Plans
No sign-in needed. Connect with RailFi Payout Plans’s own URL:
Paste it into any client that supports remote MCP servers. Your client talks to RailFi directly, not through mcp.tc.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/railfi-payout-plansAbout
RailFi Payout Plans checks stablecoin payout runs (recipients, budget, time window) and returns an approve-once pack that the owner approves in their own wallet. It can also look up public USDC and USDT Transfer events and match on-chain transfers to plan lines to show which invoices are paid, unpaid or unexpected.
The server is hosted at a remote streamable HTTP endpoint. No sign-in or API key is needed. It is non-custodial: the tools validate and reconcile, and they never move funds or handle keys.
What you can do
- Create bounded payout plans with recipients, budget and time window
- Validate plans for bad addresses, duplicates and over-budget totals
- Look up public USDC/USDT transfers to given recipients (read-only)
- Reconcile on-chain transfers against plan lines
- Identify paid, unpaid and unexpected transfers
Tools 4
create_payout_planValidate a bounded stablecoin payout run and return an approve-once pack for the owner's wallet.
validate_payout_planCheck a plan for bad addresses, bad amounts, duplicates, inverted windows and over-budget totals.
reconcile_payoutsMatch on-chain transfers to plan lines and report paid, unpaid or unexpected transfers.
fetch_transfersRead-only lookup of public USDC/USDT Transfer events to recipients over recent blocks.
Read from the live server on 18 Nov 2026.
Example prompts
Validate this payout CSV for bad addresses and duplicates before I approve it.
Create a USDC payout plan with a 5000 budget for these three recipients.
Fetch recent USDT transfers to these addresses and reconcile them with my invoices.
Which invoices in my payout plan are still unpaid?
Set up
Every client connects to railfi.xyz. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http railfi-payout-plans https://railfi.xyz/api/mcp- Start Claude Code and type
/mcp. railfi-payout-plans should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it RailFi Payout Plans and paste this URL:
https://railfi.xyz/api/mcp- Click Add. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://railfi.xyz/api/mcpand click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://railfi.xyz/api/mcpas the server URL, then for authentication choose No authentication. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"railfi-payout-plans": {
"url": "https://railfi.xyz/api/mcp"
}
}
}VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"railfi-payout-plans","type":"http","url":"https://railfi.xyz/api/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"railfi-payout-plans": {
"type": "http",
"url": "https://railfi.xyz/api/mcp"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"railfi-payout-plans": {
"serverUrl": "https://railfi.xyz/api/mcp"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add railfi-payout-plans --url https://railfi.xyz/api/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.railfi-payout-plans]
url = "https://railfi.xyz/api/mcp"Gemini CLI
gemini mcp add --transport http railfi-payout-plans https://railfi.xyz/api/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"railfi-payout-plans": {
"type": "http",
"url": "https://railfi.xyz/api/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://railfi.xyz/api/mcp.
Embed
Show RailFi Payout Plans in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/railfi-payout-plans)<a href="https://mcp.tc/i/railfi-payout-plans"><img src="https://mcp.tc/i/railfi-payout-plans/badge.svg" alt="RailFi Payout Plans on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/railfi-payout-plans.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/railfi-payout-plans" title="RailFi Payout Plans on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/railfi-payout-plans.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the RailFi Payout Plans card to your site.
Add the mcp.tc card for RailFi Payout Plans, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/railfi-payout-plans.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="railfi-payout-plans"><a href="https://mcp.tc/i/railfi-payout-plans">RailFi Payout Plans on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/railfi-payout-plans)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:40 UTC.
FAQ
Can I paste mcp.tc/i/railfi-payout-plans into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://railfi.xyz/api/mcp, so your client talks to RailFi Payout Plans directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does RailFi Payout Plans need an API key or a sign-in?
No. RailFi Payout Plans doesn’t ask for an account or key.
Is RailFi Payout Plans a remote or a local server?
Remote. RailFi hosts it at https://railfi.xyz/api/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can RailFi Payout Plans do?
It has 4 tools, including create_payout_plan, validate_payout_plan and reconcile_payouts. You can create bounded payout plans with recipients, budget and time window, validate plans for bad addresses, duplicates and over-budget totals and look up public USDC/USDT transfers to given recipients (read-only).
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to RailFi Payout Plans?
Yes. RailFi Payout Plans’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read RailFi Payout Plans’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with RailFi. This page was built from RailFi Payout Plans’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.