SCRIPTMASTERLABS — GatePay

com.scriptmasterlabsPublished by scriptmasterlabs.comv0.5.1Updated Nov 5, 2026

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

The publisher's own server: SCRIPTMASTERLABS — B20 Truth

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for GatePay that lets an assistant inspect payment routing policy, quote payouts, and execute policy-gated Arc payouts.

What you can do
  • Check GatePay service health, route-auth configuration, active policy summary, mock-settlement state and ledger integrity
  • Read the active routing policy: live rail/network, per-transaction and daily caps, hourly settled limit, allowlist state and the 50 bps fee
  • Quote a payout by running the same policy evaluation as the route endpoint, returning allow/deny, reasons and the fee split, without settling or writing ledger entries
  • Execute a payout through the existing GatePay route logic, subject to the same caps, allowlist, ledger and Arc settlement path
When to use it
Use it when an assistant needs to check or explain GatePay routing policy and caps, preview whether a payout would be allowed and what it would cost, or actually submit a payout that must pass the configured policy.
Requirements
A remote streamable HTTP endpoint; no package or local runtime. The payout execution tool only runs when the MCP HTTP request carries the X-GatePay-Route-Key header; no other credentials are declared.
Before you install
The route tool moves money and writes ledger entries, so a wrong or overly broad policy can cause real payouts. Execution depends on the X-GatePay-Route-Key header, which is a secret that must be kept out of logs and shared configs. Status and quote tools are free and move no money; check the policy and quote first.

Installation

In SourceWeft

  1. Open SCRIPTMASTERLABS — GatePay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.scriptmasterlabs%2Fgatepay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "scriptmasterlabs-gatepay": {
      "type": "http",
      "url": "https://gatepay.onrender.com/mcp"
    }
  }
}

Tools

4

gatepay_status

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

Takes no parameters.

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.

Takes no parameters.

gatepay_quote

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.

Parametersmemoamountrequireddestinationrequired

gatepay_route

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.

Parametersmemoamountrequireddestinationrequired

Version history

2
  1. v0.5.1LatestNov 5, 2026
  2. v0.5.0Oct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Scriptmasterlabs integrations