MandateShield AI Payment Authority
Server Details
Verifies signed AI payment authority before execution. Returns ALLOW, REVIEW or BLOCK; never pays.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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
2 toolscheck_ai_payment_authorityCheck AI Payment AuthorityIdempotentInspect
Analyze whether a proposed AI-agent purchase fits supplied policy facts. This v1 tool is non-executable and always returns enforcement_authorized=false; use the strict cryptographic tool for a production gate. Never send payment credentials or private keys.
| Name | Required | Description | Default |
|---|---|---|---|
| amount | Yes | ||
| limits | No | Sandbox analysis policy. Live v2 ignores caller policy and loads the registered mandate. | |
| network | No | Exact network or chain identifier; required for atomic X402 payments. | |
| purpose | No | Non-sensitive plain-language purchase purpose. | |
| agent_id | Yes | Stable identifier for the acting AI agent. | |
| asset_id | No | Exact token or asset identifier; required for atomic X402 payments. | |
| protocol | Yes | Source protocol or CUSTOM for a normalized envelope. | |
| resource | No | Exact paid resource identifier; required for atomic X402 payments. | |
| created_at | No | ||
| expires_at | No | ||
| mandate_id | Yes | Stable identifier for the user-approved authority. | |
| intent_hash | No | ||
| merchant_id | Yes | Stable identifier for the final seller or payee. | |
| user_consent | No | ||
| checkout_hash | No | Digest or stable identifier for the exact final checkout. | |
| idempotency_key | Yes | Unique identifier for this intended payment attempt. | |
| credential_binding | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| mode | Yes | |
| risk | Yes | |
| error | No | |
| score | Yes | Deterministic control-coverage indicator, not a calibrated probability of fraud or loss. |
| receipt | Yes | |
| controls | Yes | |
| decision | Yes | |
| findings | Yes | |
| protocol | Yes | |
| persisted | Yes | |
| checked_at | Yes | |
| recommended_action | Yes | |
| enforcement_authorized | Yes | True only when strict live verification durably creates a trusted, consumable execution reservation. It never permits a direct provider call. |
verify_cryptographic_payment_authorityVerify Cryptographic Payment AuthorityIdempotentInspect
Fail-closed production verification for JWS, an AP2-shaped closed-payment SD-JWT projection with RFC 9901 KB-JWT, or normalized TAP-shaped RFC 9421-style evidence. Full AP2 checkout/delegate-chain and Visa TAP structured-field/trust-store processing remain external. A qualifying live ALLOW creates only a short RESERVED authorization and cumulative-budget allocation. This MCP tool never executes payment and exposes no processor transition: a separate trusted gateway with an audience-bound PROCESSOR key must CONSUME before one provider submission, then COMMIT or RELEASE.
| Name | Required | Description | Default |
|---|---|---|---|
| envelope | Yes | ||
| evidence | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| mode | Yes | |
| risk | Yes | |
| error | No | |
| score | Yes | Deterministic control-coverage indicator, not a calibrated probability of fraud or loss. |
| receipt | Yes | |
| controls | Yes | |
| decision | Yes | |
| findings | Yes | |
| protocol | Yes | |
| assurance | Yes | |
| persisted | Yes | |
| checked_at | Yes | |
| transparency | Yes | |
| signed_receipt | Yes | |
| recommended_action | Yes | |
| enforcement_authorized | Yes | True only when strict live verification durably creates a trusted, consumable execution reservation. It never permits a direct provider call. |
| execution_authorization | Yes |
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!