gate402 merchant checkout
by ogenalabs.com · remote · no sign-in to list tools · v0.1.0 · published by com.ogenalabs
Drop-in x402 checkout for merchants: issue terms, verify payment. $0.01 each.
2 tools: 2 change things.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things2Claude Code: ask: see these tools
- Only reads0Claude Code: allow
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http gate402-x402 https://api.ogenalabs.com/api/gate402/mcpFindings
Matches of fixed checks, with the text they matched.
- Warnverify_checkout
The server marks "verify_checkout" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "verify_checkout" says "checkout": a word for a change.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
2 tools
Changes things 2Claude Code: ask
create_checkoutIssue buyer-facing x402 payment terms for one merchant order: funds settle payer to merchant directly.No findings
Why it is in this group
- The name "create_checkout" says "create": a word for a change.
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.1 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.
Findings
- Warn
The server marks "verify_checkout" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "verify_checkout" says "checkout": a word for a change.
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.
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/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .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. It assumes the server is installed as gate402-x402. Review it before you use it.