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.
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.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
1 toolguild_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.
| Name | Required | Description | Default |
|---|---|---|---|
| policy | No | ||
| api_key | No | ||
| payment | Yes | The exact target payment being authorized before wallet signing. | |
| capability | No | ||
| ttl_seconds | No | ||
| x402_payment | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityAmaintenanceBefore an AI agent pays an x402 endpoint, checks whether it's safe to pay: liveness, scam/anomaly scan (payTo hijack, bait-and-switch, honeypot), and on-chain receiver verification. ~70% of x402 endpoints are dead or scams.3MIT
- AlicenseAqualityBmaintenanceA pre-payment safety gate for x402 that screens payment metadata for PII, enforces spending policies, and detects replay attacks before signing.32MIT
- AlicenseAqualityAmaintenancex402-trust gives AI agents a "check before you pay" layer for the x402 ecosystem.12242MIT
- Alicense-qualityAmaintenanceA budget-bound x402 payment wallet for AI agents: it autonomously pays HTTP 402 payment-gated URLs across every major chain (EVM, Solana, and many non-EVM families). Self-custodial and backendless, your key, your RPC, with spend caps enforced before any on-chain send.7MIT
Your Connectors
Sign in to create a connector for this server.