Cross-Rail Settlement Binder is answering right now. Last checked 7 min ago. It exposes 4 tools.
Multi-rail settlement binder MCP. binder_verify proves integrity only — not settlement.
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
claude mcp add crs-binder --transport http https://crs-binder.fly.dev/mcp
https://crs-binder.fly.dev/mcp
[mcp_servers.crs-binder]
url = "https://crs-binder.fly.dev/mcp"
{
"mcpServers": {
"crs-binder": {
"url": "https://crs-binder.fly.dev/mcp"
}
}
}
{
"servers": {
"crs-binder": {
"type": "http",
"url": "https://crs-binder.fly.dev/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
binder_append
binder_seal
binder_verify
health
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://crs-binder.fly.dev/mcp | streamable-http | answering | 271 ms | 7 min ago |
Payment-rail-independent intent-to-effect integrity for consequential agent actions.
Read-only queries over Aileron audit journals: verify integrity, search recorded tool calls
Multi-provider AI router with x402 micropayment settlement on Base L2. 1% flat fee.
Verify crypto payments really settled and how much arrived. 20 chains. Read only, no API key.
Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index.
Concurrent two-client overlap probe proving MCP servers do not cross-deliver tool results.
Agent settlement protocol — discover, negotiate, settle, and verify with XAP.
Multi-instance read-only MCP server for ServiceNow
Answers built from our own checks of this server.