Policy-gated Arc payment routing: hard caps, signed mandates, hash-chained proof.
Connect Remote server
claude mcp add --transport http gatepay https://gatepay.onrender.com/mcp
{
"mcpServers": {
"gatepay": {
"url": "https://gatepay.onrender.com/mcp"
}
}
}
{
"servers": {
"gatepay": {
"type": "http",
"url": "https://gatepay.onrender.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://gatepay.onrender.com/mcp
Tools 4 found in our last check
gatepay_statusGatePay service status: health, route-auth configured state, active policy summary, mock-settlement state and ledger integrity. Free; moves no money.
gatepay_policyThe active GatePay routing policy: live rail/network, per-transaction and daily caps, settled-per-hour limit, target allowlist state and the 50 bps fee. Free; moves no money.
gatepay_quoteQuote a payout: runs the same policy evaluation POST /v1/route would, returning allow/deny, the reasons and the fee split. Settles NOTHING and writes NO ledger entry.
gatepay_routeExecute a payout through the existing GatePay route logic (same caps, allowlist, ledger and Arc settlement path as POST /v1/route). Executes ONLY when the MCP HTTP request carries the X-GatePay-Route-Key header; a missing or wrong key is a hard refusal before any policy, ledger…
Details
| Endpoint | https://gatepay.onrender.com/mcp (Streamable HTTP) |
| First published | 5 Nov 2026 |
| Last updated | 5 Nov 2026 |
| Registry name | com.scriptmasterlabs/gatepay |
More finance and crypto servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
