Skip to main content
Glama

SCRIPTMASTERLABS — GatePay

Server Details

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

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

The read/evaluate/execute triad is clearly separated: gatepay_policy reads config, gatepay_quote dry-runs the evaluation, gatepay_route executes, and gatepay_status reports service health. The one soft overlap is that gatepay_status also returns an 'active policy summary' while gatepay_policy returns the full policy, so an agent asking 'what is the current policy?' could reasonably pick either.

Naming Consistency5/5

Every tool uses the same gatepay_ prefix followed by a single short, lowercase token (policy, quote, route, status), with no camelCase or mixed verb styles. The pattern is fully predictable and readable.

Tool Count4/5

Four tools is a tight, purpose-built surface where each has a clear job: inspect policy, simulate, execute, and monitor. It is on the lean side — there is no tool for inspecting ledger entries or past payouts — but nothing is redundant or filler.

Completeness3/5

The routing lifecycle (policy read, quote, route, status) is covered, but there is no way to list past payouts or read ledger entries for reconciliation, and the policy is read-only with no way to update caps or the allowlist. Agents can execute and simulate, but hit dead ends when they need history or configuration changes.

Available Tools

4 tools
gatepay_policyGatePay Routing PolicyA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

gatepay_quoteGatePay Payout QuoteA
Read-onlyIdempotent
Inspect

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.

Inputs: amount (required), destination (required), memo.

gatepay_routeGatePay Execute PayoutA
Destructive
Inspect

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.

Inputs: amount (required), destination (required), memo.

gatepay_statusGatePay Service StatusA
Read-onlyIdempotent
Inspect

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

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to propose wallet payments while a local, human-authored policy decides whether each transaction is approved, requires human confirmation, or is refused, and records every decision in a signed, append-only ledger.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to make payments with strict spending limits enforced by signed mandates, preventing unauthorized fund movement beyond predefined caps and allowlists.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Cryptographic proof of consent for AI agents. Sign before you act. Policy engine enforces spending caps, action whitelists, and escalation rules. Independently verifiable by anyone.
      10
      2
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources