Skip to content

RailFi Payout Plans

by railfi.xyz · remote · no sign-in to list tools · v0.1.0 · published by xyz.railfi

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

Final · 2
CompareRegistry entry

4 tools: 2 do something that can't be undone and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http payout-plans https://railfi.xyz/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Can't be undone 2Claude Code: ask
  • create_payout_planValidate a bounded stablecoin payout run (recipients, budget, time window) and return an approve-once pack the OWNER approves in their own wallet.No findings

    Why it is in this group

    • The name "create_payout_plan" says "create": a word for a change.
    • The name "create_payout_plan" also says "payout": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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.
  • reconcile_payoutsMatch on-chain transfer records (recipient, amount, txHash) to plan lines and report which invoices are paid, unpaid, or unexpected transfers.No findings

    Why it is in this group

    • The name "reconcile_payouts" says "payout": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Match on-chain transfer records (recipient, amount, txHash) to plan lines and report which invoices are paid, unpaid, or unexpected transfers.
Only reads 2Claude Code: allow
  • fetch_transfersRead-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.No findings

    Why it is in this group

    • The name "fetch_transfers" says "fetch": a word for reading.
    Description, as the server wrote it
    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.
  • validate_payout_planCheck a payout plan for bad addresses, bad amounts, duplicates, inverted window and over-budget totals.No findings

    Why it is in this group

    • The name "validate_payout_plan" says "validate": a word for reading.
    Description, as the server wrote it
    Check a payout plan for bad addresses, bad amounts, duplicates, inverted window and over-budget totals.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http payout-plans https://railfi.xyz/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__payout-plans__validate_payout_plan",
      "mcp__payout-plans__fetch_transfers"
    ],
    "ask": [
      "mcp__payout-plans__create_payout_plan",
      "mcp__payout-plans__reconcile_payouts"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as payout-plans. Review it before you use it.