SCRIPTMASTERLABS — GatePay
REMOTE · GATEPAY.ONRENDER.COM
Policy-gated Arc payment routing: hard caps, signed mandates, hash-chained proof.
Available components
Last scanned (6 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
Recent critical change
Authorization (29 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (gatepay_route). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 286 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +2
- Authorization: unverified → fail ▼ critical
- Tool “gatepay_route” is now declared destructive security
- Stability: unverified → 0.03 ▲ functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- 28 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://gatepay.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gatepay.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gatepay.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://gatepay.onrender.com/mcp | HTTPS enforced | 301 | https://gatepay.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gatepay_policy ~50
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
gatepay_quote ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in USDC. |
| destination | string | yes | Destination wallet address on Arc. |
| memo | string | – | Optional memo recorded with the request payload. |
No output schema declared.
No examples provided.
gatepay_route ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in USDC. |
| destination | string | yes | Destination wallet address on Arc. |
| memo | string | – | Optional memo recorded with the request payload. |
No output schema declared.
No examples provided.
gatepay_status ~39
GatePay service status: health, route-auth configured state, active policy summary, mock-settlement state and ledger integrity. Free; moves no money.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SCRIPTMASTERLABS — GatePay MCP server?
SCRIPTMASTERLABS — GatePay is a hosted endpoint at https://gatepay.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gatepay.onrender.com
claude mcp add --transport http com-scriptmasterlabs-gatepay 'https://gatepay.onrender.com/mcp'
What is the SCRIPTMASTERLABS — GatePay MCP server?
SCRIPTMASTERLABS — GatePay is an MCP server listed in the public MCP registry as com.scriptmasterlabs/gatepay. Policy-gated Arc payment routing: hard caps, signed mandates, hash-chained proof. This page covers its hosted endpoint (https://gatepay.onrender.com/mcp).
Is the SCRIPTMASTERLABS — GatePay MCP server safe to use?
SCRIPTMASTERLABS — GatePay scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SCRIPTMASTERLABS — GatePay MCP server expose?
SCRIPTMASTERLABS — GatePay exposes 4 tools: gatepay_status, gatepay_policy, gatepay_quote, gatepay_route. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.
Does the SCRIPTMASTERLABS — GatePay MCP server require authentication?
No. We connected to SCRIPTMASTERLABS — GatePay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SCRIPTMASTERLABS — GatePay MCP server still maintained?
SCRIPTMASTERLABS — GatePay is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.