Skip to main content
Glama

x402-payment-safety

Server Details

Authorize x402 payments before signing with request-bound, signed safety decisions.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
AgentTanuki/agent-guild
GitHub Stars
1
Server Listing
Agent Guild

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.

Tool Definition Quality

Score is being calculated. Check back soon.

Available Tools

1 tool
guild_x402_payment_safetyAuthorize an x402 payment before signingInspect

PAID. Call this immediately BEFORE signing an x402 payment envelope.

Returns one short-lived, Guild-signed AGPD-1 allow/block credential bound to the exact target payment: scheme, CAIP-2 network, asset contract, atomic amount, payee and resource URL, plus optional capability and policy thresholds. Verify it offline with POST /wallet-binding/decision/verify.

This is the native MCP transport for the existing HTTP POST /wallet-binding/decision product. An unpaid call returns a complete x402 v2 challenge for the exact request digest. Retry with the official _meta['x402/payment'] carrier; adapters that cannot set request metadata may pass the identical signed PaymentPayload as x402_payment. Conflicting carriers fail closed before facilitator verification or settlement.

The decision is issued before metering, so malformed inputs or signing failures are never charged. api_key uses sandbox credits and is never external revenue. The free identity-only alternative is GET /wallet-binding/resolve.

ParametersJSON Schema
NameRequiredDescriptionDefault
policyNo
api_keyNo
paymentYesThe exact target payment being authorized before wallet signing.
capabilityNo
ttl_secondsNo
x402_paymentNo

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.