SCRIPTMASTERLABS — GatePay is an MCP server published by com.scriptmasterlabs, hosted at gatepay.onrender.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including gatepay_status, gatepay_policy, gatepay_quote, gatepay_route.
Policy-gated Arc payment routing: hard caps, signed mandates, hash-chained proof.
645 connections through 4 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
GatePay service status: health, route-auth configured state, active policy summary, mock-settlement state and ledger integrity. Free; moves no money.
No parameters.
{
"name": "gatepay_status",
"title": "GatePay Service Status",
"description": "GatePay service status: health, route-auth configured state, active policy summary, mock-settlement state and ledger integrity. Free; moves no money.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"title": "GatePay Service Status",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
The 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.
No parameters.
{
"name": "gatepay_policy",
"title": "GatePay Routing Policy",
"description": "The 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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"title": "GatePay Routing Policy",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Quote 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.
| Parameter | Type | Description |
|---|---|---|
| memo | string | Optional memo recorded with the request payload. |
| amount * | number | Amount in USDC. |
| destination * | string | Destination wallet address on Arc. |
{
"name": "gatepay_quote",
"title": "GatePay Payout Quote",
"description": "Quote 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.",
"inputSchema": {
"type": "object",
"required": [
"amount",
"destination"
],
"properties": {
"memo": {
"type": "string",
"description": "Optional memo recorded with the request payload."
},
"amount": {
"type": "number",
"description": "Amount in USDC.",
"exclusiveMinimum": 0
},
"destination": {
"type": "string",
"description": "Destination wallet address on Arc."
}
}
},
"annotations": {
"title": "GatePay Payout Quote",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Execute 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 or settlement step runs.
| Parameter | Type | Description |
|---|---|---|
| memo | string | Optional memo recorded with the request payload. |
| amount * | number | Amount in USDC. |
| destination * | string | Destination wallet address on Arc. |
{
"name": "gatepay_route",
"title": "GatePay Execute Payout",
"description": "Execute 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 or settlement step runs.",
"inputSchema": {
"type": "object",
"required": [
"amount",
"destination"
],
"properties": {
"memo": {
"type": "string",
"description": "Optional memo recorded with the request payload."
},
"amount": {
"type": "number",
"description": "Amount in USDC.",
"exclusiveMinimum": 0
},
"destination": {
"type": "string",
"description": "Destination wallet address on Arc."
}
}
},
"annotations": {
"title": "GatePay Execute Payout",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
}
}GatePay by ScriptMasterLabs: policy-gated payout routing on the Arc rail. Free read-only tools: gatepay_status (service health, route-auth state, active policy summary, mock-settlement state and ledger integrity), gatepay_policy (live rail/network, per-transaction and daily caps, settled-per-hour limit, target allowlist state and the 50 bps fee), and gatepay_quote (runs the same policy evaluation as a route — allow/deny with reasons and the fee split — but settles nothing and writes no ledger entry). gatepay_route executes a real payout through the same caps, allowlist, ledger and Arc settlement path as POST /v1/route, and runs only when the MCP HTTP request carries a valid X-GatePay-Route-Key header; a missing or wrong key is refused before any policy, ledger or settlement step.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.