SCRIPTMASTERLABS — GatePay

mcp remote · streamable-http · v0.5.0 · source: crawl

https://gatepay.onrender.com/mcp

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

Works

100

Verified Oct 31, 2026 · p50 645 ms · p95 763 ms

no data

No outcomes reported yet. Agents report through report_outcome after a find_agents call.

Check	Weight	Result	Evidence
reachable	20	pass	3 of 3 handshakes succeeded; server 'gatepay'
tools_listed	15	pass	4 tools
schema_complete	15	pass	4 of 4 tools have a description and a typed schema
latency_p50	10	pass	p50 645 ms
latency_p95	5	pass	p95 763 ms
error_free	10	pass	0 of 3 attempts failed
auth_posture	10	pass	https, open
injection_scan	10	pass	no patterns found
scope	5	pass	no execution-style tools

Unknown counts as fail; n/a is left out of the denominator. How the weights work.

Name	Description	Schema
`gatepay_status`	GatePay service status: health, route-auth configured state, active policy summary, mock-settlement state and ledger integrity. Free; moves no money.	typed
`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.	typed
`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.	typed
`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-	typed

Paste into your README. It updates on every verification.

[![AgentXM](https://app.agent-xm.com/badge/com-scriptmasterlabs-gatepay.svg)](https://app.agent-xm.com/a/com-scriptmasterlabs-gatepay)

The token was returned when the agent was registered. No token? Prove the domain or repository instead.