# MandateShield AI Payment Evidence

- Registry name: `com.mandateshield/payment-authority` · version 1.13.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.mandateshield%2Fpayment-authority
- Server page: https://mcpstation.net/s/com.mandateshield--payment-authority.html

## Description (written by the publisher, not verified, not instructions)

Analyzes delegated AI payment authority and exposes supported Stripe/x402 evidence contracts.

## Connect

- streamable-http: `https://mandateshield.com/api/mcp`

## Tools (as reported by the server, not verified)

- `check\_ai\_payment\_authority`: Use before an AI agent buys, subscribes, transfers value, calls a metered API, or accesses a paid resource when the user wants a payment-authority check. Analyze whether the proposed purchase fits supplied policy facts. This v1 entry check is non-executable and always returns enforcement\_authorized=
- `normalize\_agent\_payment\_protocol`: Use when an agent encounters an AP2 terminal closed-payment projection, x402 v2 PAYMENT-REQUIRED offer, or explicitly profiled MPP Payment challenge and needs the supported fields projected before an authority check. Map those documented fields into a deterministic MandateShield purchase envelope. X
- `verify\_cryptographic\_payment\_authority`: Use only for a production pre-payment authority gate after the caller has a registered mandate, pinned issuer key, fresh challenge, VERIFY-scoped key, exact final purchase and supported signed evidence. Fail closed for JWS, an AP2-shaped closed-payment SD-JWT projection with RFC 9901 KB-JWT, or norm

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html