SCRIPTMASTERLABS — GatePay

Policy-gated Arc payment routing: hard caps, signed mandates, hash-chained proof.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
65%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~400Tokens (tool definitions)
~575 BTypical response size
Minimal attention impact (0.31% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "gatepay": {
      "url": "https://gatepay.onrender.com/mcp"
    }
  }
}

Remote endpoints

https://gatepay.onrender.com/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪gatepay_status

GatePay service status: health, route-auth configured state, active policy summary, mock-settlement state and ledger integrity. Free; moves no money.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
⚪gatepay_policy

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟡gatepay_quote(amount, destination, memo)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "amount": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Amount in USDC."
    },
    "destination": {
      "type": "string",
      "description": "Destination wallet address on Arc."
    },
    "memo": {
      "type": "string",
      "description": "Optional memo recorded with the request payload."
    }
  },
  "required": [
    "amount",
    "destination"
  ]
}
🟡gatepay_route(amount, destination, memo)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "amount": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Amount in USDC."
    },
    "destination": {
      "type": "string",
      "description": "Destination wallet address on Arc."
    },
    "memo": {
      "type": "string",
      "description": "Optional memo recorded with the request payload."
    }
  },
  "required": [
    "amount",
    "destination"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools