binder_seal — Cross-Rail Settlement Binder MCP Tool
binder_seal
(binder seal) is one of 4 tools on the
Cross-Rail Settlement Binder
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call binder_seal from your client
- Claude Code Cross-Rail Settlement Binder binder_seal run in your project directory
- Claude Desktop Cross-Rail Settlement Binder binder_seal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cross-Rail Settlement Binder binder_seal ~/.cursor/mcp.json
- VS Code Cross-Rail Settlement Binder binder_seal .vscode/mcp.json
- Zed Cross-Rail Settlement Binder binder_seal ~/.config/zed/settings.json
- Windsurf Cross-Rail Settlement Binder binder_seal ~/.codeium/windsurf/mcp_config.json
- Cline Cross-Rail Settlement Binder binder_seal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cross-Rail Settlement Binder binder_seal ~/.gemini/settings.json
- Grok Cross-Rail Settlement Binder binder_seal .mcp.json (in your project root)
- ChatGPT Cross-Rail Settlement Binder binder_seal Settings → Connectors → Advanced → Developer mode
- Claude.ai Cross-Rail Settlement Binder binder_seal Settings → Connectors → Add custom connector
- LangChain Cross-Rail Settlement Binder binder_seal pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crs-binder https://crs-binder.fly.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.