RailFi Payout Plans
REMOTE · RAILFI.XYZ
Free, non-custodial tools to validate bounded USDC/USDT payout plans and reconcile payouts.
Available components
Last scanned (9 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 454 tokens (~113/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
- Schema quality: 335 → 454 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “fetch_transfers” functional
- 14 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://railfi.xyz/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.railfi.xyz | CN=YR2,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | RSA 2048 | SHA256-RSA | 6b2182f1e4ae18c7e822f1255bbf32a2582 |
| SANs: *.railfi.xyz, railfi.xyz | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of railfi.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| railfi.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://railfi.xyz/api/mcp | Verified | 200 | |
| http (plaintext) | http://railfi.xyz/api/mcp | HTTPS enforced | 308 | https://railfi.xyz/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_payout_plan ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | yes | Max total in token units, e.g. "1000" |
| csv | string | – | Optional CSV: invoice_ref,recipient,amount[,note] |
| lines | array | – | – |
| name | string | yes | – |
| network | string | yes | – |
| token | string | yes | – |
| windowEnd | string | yes | ISO 8601 |
| windowStart | string | yes | ISO 8601 |
No output schema declared.
No examples provided.
fetch_transfers ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Optional payer address |
| fromBlock | integer | – | – |
| network | string | yes | – |
| recipients | array | yes | – |
| toBlock | integer | – | Default: latest block; default range 5000 blocks |
| token | string | yes | – |
No output schema declared.
No examples provided.
reconcile_payouts ~53
Match on-chain transfer records (recipient, amount, txHash) to plan lines and report which invoices are paid, unpaid, or unexpected transfers.
| Name | Type | Req | Description |
|---|---|---|---|
| lines | array | yes | – |
| transfers | array | yes | – |
No output schema declared.
No examples provided.
validate_payout_plan ~119
Check a payout plan for bad addresses, bad amounts, duplicates, inverted window and over-budget totals.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | yes | Max total in token units, e.g. "1000" |
| csv | string | – | Optional CSV: invoice_ref,recipient,amount[,note] |
| lines | array | – | – |
| name | string | yes | – |
| network | string | yes | – |
| token | string | yes | – |
| windowEnd | string | yes | ISO 8601 |
| windowStart | string | yes | ISO 8601 |
No output schema declared.
No examples provided.
How do I install the RailFi Payout Plans MCP server?
RailFi Payout Plans is a hosted endpoint at https://railfi.xyz/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · railfi.xyz
claude mcp add --transport http xyz-railfi-payout-plans 'https://railfi.xyz/api/mcp'
What is the RailFi Payout Plans MCP server?
RailFi Payout Plans is an MCP server listed in the public MCP registry as xyz.railfi/payout-plans. Free, non-custodial tools to validate bounded USDC/USDT payout plans and reconcile payouts. This page covers its hosted endpoint (https://railfi.xyz/api/mcp).
Is the RailFi Payout Plans MCP server safe to use?
RailFi Payout Plans scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RailFi Payout Plans MCP server expose?
RailFi Payout Plans exposes 4 tools: create_payout_plan, validate_payout_plan, reconcile_payouts, fetch_transfers. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.
Does the RailFi Payout Plans MCP server require authentication?
No. We connected to RailFi Payout Plans without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RailFi Payout Plans MCP server still maintained?
RailFi Payout Plans is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.