RailFi MCP server

• Registry namexyz.railfi/payout-plansverified in the MCP registry

The registry name sits under railfi.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools4
• Server calls itselfrailfi-payout-plans
• Server version0.2.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 97 ms.

• Its tools do Match on-chain payments against invoices and flag partial or wrong tokens, but not Prepare tax reports with fiat values recorded at payment time.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score57 of 100answers 100 · does the job 50 · definitions 67 · context 100 · use 0 · connects 100 · lowered by the warning signs below
• What an agent can do with it1 of 2 use cases
• Answered100% of days7 of 7 daily checks
• Median first answer154 ms
• Space in an agent's context≈ 846 tokensthe definitions of all its tools (4), which an agent carries on every turn
• Tool definitionsC · 67 of 100
• Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 4 of 4
• Not saying whether it only reads or can destroy: 4 of 4

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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.