MandateShield AI Payment Evidence
com.mandateshield/payment-authority · v1.13.0
Analyzes delegated AI payment authority and exposes supported Stripe/x402 evidence contracts.
MCPremoteAPI keyFinanceMaps & location
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 70/100
What it does: 3 tools · 1 read, 2 write · Finance, Maps & location
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +2
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: 0
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://mandateshield.com/api/mcpTools
3 tools listed at last check
check_ai_payment_authorityUse 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_protocolUse 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. Xverify_cryptographic_payment_authorityUse 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
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/com.mandateshield/payment-authority)