RailFi Payout Plans

xyz.railfiPublished by railfi.xyzOfficial publisherv0.1.0Updated Oct 24, 2026

Free, non-custodial tools to validate bounded USDC/USDT payout plans and reconcile payouts.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Non-custodial remote MCP server for validating bounded USDC/USDT payout plans and reconciling on-chain transfers against them.

What you can do
  • Create and validate payout plans: check recipients, amounts, duplicates, budget totals and time windows, and export an approve-once pack for the owner's wallet
  • Look up public USDC/USDT Transfer events to given recipients over recent blocks via a public RPC
  • Reconcile on-chain transfers against plan lines and report which invoices are paid, unpaid or unexpected
When to use it
Useful when an assistant helps turn invoice or payout rows into a bounded stablecoin payout run that a human approves in their own wallet, or when you need to check which planned payouts actually landed on chain. It is a planning and reconciliation aid, not a payment executor.
Requirements
Remote streamable HTTP endpoint; no API key or OAuth. Rate limited to 60 requests per minute per IP. Read-only transfer lookups rely on a public RPC and cover up to 10000 recent blocks on Polygon, Base, Ethereum and Arbitrum.
Before you install
The server states it never holds funds or keys and does not execute payments; approval and signing happen in the owner's own wallet. Reconcile results depend on public RPC data and the block window, so treat them as a report rather than proof of settlement. Plan contents and recipient addresses are sent to a third-party service.

Installation

In SourceWeft

  1. Open RailFi Payout Plans in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/xyz.railfi%2Fpayout-plans/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "railfi-payout-plans": {
      "type": "http",
      "url": "https://railfi.xyz/api/mcp"
    }
  }
}

README

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

WhatURL
MCP (streamable HTTP, JSON-RPC, protocol 2025-06-18)https://railfi.xyz/api/mcp
A2A agent cardhttps://railfi.xyz/.well-known/agent-card.json
Web app (plans)https://railfi.xyz/plans?src=site
Early-bird betahttps://railfi.xyz/beta?src=site

Tools

ToolUse when
create_payout_planYou need to validate recipients, amounts, total budget and time window, then export an approve-once pack for the owner's wallet
validate_payout_planYou want to check a plan without creating an export
fetch_transfersRead-only public USDC/USDT Transfer lookup (Polygon, Base, Ethereum, Arbitrum)
reconcile_payoutsTransfers landed and you need to mark lines paid (tx hash) or skipped and report progress

Install / connect (remote)

json
{ "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/send is not implemented.
  • Software only — not a money transmitter, bank, or custodian.

Contact

[email protected] · https://railfi.xyz

Source: README.md at commit c088174

Tools

4

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.

ParameterscsvnamerequiredlinestokenrequiredbudgetrequirednetworkrequiredwindowEndrequiredwindowStartrequired

validate_payout_plan

Check a payout plan for bad addresses, bad amounts, duplicates, inverted window and over-budget totals.

ParameterscsvnamerequiredlinestokenrequiredbudgetrequirednetworkrequiredwindowEndrequiredwindowStartrequired

reconcile_payouts

Match on-chain transfer records (recipient, amount, txHash) to plan lines and report which invoices are paid, unpaid, or unexpected transfers.

Parameterslinesrequiredtransfersrequired

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.

ParametersfromtokenrequirednetworkrequiredtoBlockfromBlockrecipientsrequired

Version history

1
  1. v0.1.0LatestOct 14, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.