Paid tools for any MCP client. No key handed over.
/.well-known/mcp.json · /api/mcp (JSON-RPC POST)
IronBridge ships an MCP server your agent connects to like any other — except the money side runs through the gate, not the model. Your client never holds a spending key, and the gate's decisions land on a public hash-chain you can re-walk yourself.
End to end: connect → call → verify.
1 — Connect. Run the server locally, or point your MCP client straight at the hosted endpoint.
npx @ironbridgefoundation/ironbridge-mcp-server # or use the hosted endpoint (JSON-RPC 2.0 over HTTP POST): https://ironbridge.foundation/api/mcp
2 — Call. Standard MCP: initialize, tools/list, tools/call. Seven tools answer live today — stats, health, status, version, token, constitution, membership count — all pulled from the running operation, nothing canned.
3 — Verify. Don't take the answers on faith. Every gate decision lands on the LAW-25 hash-chain — paste any receipt at /verify, or re-walk the chain yourself at /api/law25/verify. No account, no key.
Pair it with the paid lanes.
The same gate prices real calls at $0.10 USDC on Base across three public endpoints: BNKR, GITLAWB, and Page Audit. The current transport is IronBridge’s pay-then-prove transaction-hash extension; standard x402 v2 settlement is not yet enabled. Probe the services at /live or /demo. (Public npm package: @ironbridgefoundation/ironbridge-mcp-server 0.2.0 — installed and stranger-smoke-tested 2026-08-30.)
Who holds what.
You hold your wallet and your keys. The MCP server holds neither — it can relay a request and show you the operation, but a spend only clears if the gate under the model says so. That is the whole point.