Skip to content

Cross-Rail Settlement Binder

by arnopiva · remote · no sign-in to list tools · v0.1.1 · published by GitHub user arnopiva

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

Changes · 4
CompareRegistry entry

4 tools: 4 change things.

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 crs-binder https://crs-binder.fly.dev/mcp

Tools

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

4 tools

Changes things 4Claude Code: ask
  • binder_appendAppend one settlement leaf (x402 | stripe_mpp | agentcore) under your task_id.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Append one settlement leaf (x402 | stripe_mpp | agentcore) under your task_id. Free.
  • binder_sealSeal ≥2 distinct rails under task_id into a portable Ed25519 binder (~$0.05 USDC on Base when paid).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Seal ≥2 distinct rails under task_id into a portable Ed25519 binder (~$0.05 USDC on Base when paid).
  • binder_verifyVerify binder integrity (sig + ordered leaf hashes).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify binder integrity (sig + ordered leaf hashes). Does not prove underlying settlement.
  • healthLiveness, rails, pubkey, paid/listing flags.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Liveness, rails, pubkey, paid/listing flags.

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.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http crs-binder https://crs-binder.fly.dev/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": [],
    "ask": [
      "mcp__crs-binder__health",
      "mcp__crs-binder__binder_append",
      "mcp__crs-binder__binder_seal",
      "mcp__crs-binder__binder_verify"
    ],
    "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 crs-binder. Review it before you use it.