Skip to content

gate402 merchant checkout MCP server

com.ogenalabs/gate402-x402ogenalabs.comstreamable-httpv0.1.0Scanned

Drop-in x402 checkout for merchants: issue terms, verify payment. $0.01 each.

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the gate402 merchant checkout MCP server can do

The gate402 merchant checkout MCP server is published by ogenalabs.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: create_checkout and verify_checkout), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (create_checkout and verify_checkout).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 29, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 2Claude Code: ask
  • create_checkoutIssue buyer-facing x402 payment terms for one merchant order: funds settle payer to merchant directly.Reads text others writeNo findings

    Why it is in this group

    • The name "create_checkout" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Issue buyer-facing x402 payment terms for one merchant order: funds settle payer to merchant directly. Costs $0.01 USDC per checkout. First 20 per caller per day are free.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • verify_checkoutVerify and settle the buyer payment for a checkout id.Reads text others write1 finding

    Why it is in this group

    • The name "verify_checkout" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "verify_checkout" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "verify_checkout" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Verify and settle the buyer payment for a checkout id. Free: pass the buyer paymentSignature, get back paid with the settlement transaction or pending with the reason.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: api.ogenalabs.com does not resolve.

Posture changes

  1. Nov 13, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
  2. Nov 6, 2026
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2024-11-05 to none

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "verify_checkout" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "verify_checkout" says "checkout": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none.View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
  2. PostureRemote posture changed. tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0; Protocol version: 2024-11-05 -> none.View diff
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2024-11-05 to none

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http gate402-x402 https://api.ogenalabs.com/api/gate402/mcp
claude mcp add --transport http gate402-x402 https://api.ogenalabs.com/api/gate402/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__gate402-x402__create_checkout",
      "mcp__gate402-x402__verify_checkout"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gate402-x402. Review it before you use it.

Capability tags behind 2 rules
  • mcp__gate402-x402__create_checkout untrusted-input
  • mcp__gate402-x402__verify_checkout untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.ogenalabs/gate402-x402/verify?hash=9a4cbb190589e7d0c89e992a2e2d7702b087b8c8d918472020e1dd1f92424ee2" | jq -e '.changed == false'

Pinned hash 9a4cbb190589, from Oct 29, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.ogenalabs/gate402-x402/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.ogenalabs/gate402-x402
[![Anlyon Radar](https://radar.anlyon.com/badge/com.ogenalabs/gate402-x402.svg)](https://radar.anlyon.com/servers/com.ogenalabs/gate402-x402)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:59 UTC.

gate402 merchant checkout MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the gate402 merchant checkout MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the gate402 merchant checkout MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the gate402 merchant checkout MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the gate402 merchant checkout MCP server have?

2 tools: 2 write. create_checkout and verify_checkout.

Does the gate402 merchant checkout MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the gate402 merchant checkout MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the gate402 merchant checkout MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 29, 2026.