Skip to content

RailFi Payout Plans MCP server

xyz.railfi/payout-plansrailfi.xyzstreamable-httpv0.1.0Scanned

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

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

Tools: 0 delete, 2 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RailFi Payout Plans MCP server can do

The RailFi Payout Plans MCP server is published by railfi.xyz, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_payout_plan and reconcile_payouts), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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 2Show 2 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://railfi.xyz/api/mcp: tools/list returned 4 tools to an anonymous client, including create_payout_plan (irreversible), reconcile_payouts (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as payout-plans. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/xyz.railfi/payout-plans/verify?hash=b17271022709e1fba2534af64be3d836f451adff0e3cd6c79e9e88298d099fa9" | jq -e '.changed == false'

Pinned hash b17271022709, from Nov 18, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/xyz.railfi/payout-plans/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for xyz.railfi/payout-plans
[![Anlyon Radar](https://radar.anlyon.com/badge/xyz.railfi/payout-plans.svg)](https://radar.anlyon.com/servers/xyz.railfi/payout-plans)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.

RailFi Payout Plans MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RailFi Payout Plans MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RailFi Payout Plans MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RailFi Payout Plans MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: create_payout_plan and reconcile_payouts.

What tools does the RailFi Payout Plans MCP server have?

4 tools: 2 irreversible, 2 read. create_payout_plan, reconcile_payouts, validate_payout_plan and fetch_transfers.

Does the RailFi Payout Plans MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RailFi Payout Plans MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RailFi Payout Plans MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.