Cross-Rail Settlement Binder

io.github.arnopivaPublished by GitHub account arnopivav0.1.1Updated Oct 24, 2026

Multi-rail settlement binder MCP. binder_verify proves integrity only — not settlement.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that records settlement entries from multiple payment rails under a task ID and seals them into a verifiable Ed25519 binder.

What you can do
Check server liveness, supported rails, public key and paid/listing flags with the health tool. Append a single settlement leaf from one of the x402, stripe_mpp or agentcore rails under a task ID, free of charge. Seal two or more distinct rails under a task ID into a portable Ed25519 binder, paid in USDC on Base. Verify a binder's integrity by checking its signature and ordered leaf hashes.
When to use it
Use it when you need a portable, cryptographically signed record that ties settlement entries from at least two different payment rails to the same task, and want an assistant to append entries and verify the resulting binder.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. Sealing requires at least two distinct rails under one task ID and, when paid, roughly $0.05 USDC on Base.
Before you install
Sealing can cost about $0.05 USDC on Base, so it spends funds. Verification proves only binder integrity, not that the underlying settlement actually occurred. Appending writes entries under your task ID to a third-party service.

Installation

In SourceWeft

  1. Open Cross-Rail Settlement Binder 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/io.github.arnopiva%2Fcrs-binder/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": {
    "cross-rail-settlement-binder": {
      "type": "http",
      "url": "https://crs-binder.fly.dev/mcp"
    }
  }
}

Tools

4

health

Liveness, rails, pubkey, paid/listing flags.

Takes no parameters.

binder_append

Append one settlement leaf (x402 | stripe_mpp | agentcore) under your task_id. Free.

Parametersleafrequiredtask_idrequired

binder_seal

Seal ≥2 distinct rails under task_id into a portable Ed25519 binder (~$0.05 USDC on Base when paid).

Parameterstask_idrequiredx402_proof

binder_verify

Verify binder integrity (sig + ordered leaf hashes). Does not prove underlying settlement.

Parametersbinderrequired

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

83% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.