All servers · Payments & accounting

MandateShield AI Payment Evidence

com.mandateshield/payment-authority · v1.13.0

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Can write (some tools are not declared read-only)
Capabilities declared	resources, tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

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

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

claude mcp add --transport http payment-authority https://mandateshield.com/api/mcp

{
  "mcpServers": {
    "payment-authority": {
      "url": "https://mandateshield.com/api/mcp"
    }
  }
}

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

Website · JSON · Text for agents · Registry updated 2026-07-28