Lets an assistant check whether a proposed AI-agent payment fits supplied policy facts and normalize payment-protocol fields before an authority check.
What you can do
Provides three tools around delegated AI payment authority. check_ai_payment_authority analyzes whether a proposed purchase, subscription, transfer, metered API call or paid resource access fits supplied policy facts; the v1 entry check is non-executable and always returns enforcement_authorized. normalize_agent_payment_protocol maps documented fields from AP2 closed-payment projections, x402 v2 PAYMENT-REQUIRED offers and profiled MPP Payment challenges into a deterministic purchase envelope. verify_cryptographic_payment_authority is a production pre-payment gate that fails closed unless a registered mandate, pinned issuer key, fresh challenge, VERIFY-scoped key and supported signed证据 are 均
When to use it
Use it when an AI agent is about to buy, subscribe, transfer value, call a metered API or access a paid resource and you want a policy-based authority check first, or when you need to normalize AP2, x402 or MPP payment fields before such a check.
Requirements
A remote streamable HTTP endpoint at mandateshield.com; no local package. An optional VERIFY-scoped API key is supplied in the Authorization header, prefixed with Bearer. Production verification additionally requires a registered mandate, a pinned issuer key, a fresh challenge and supported signed evidence.
Before you install
The Authorization header carries a secret API key; use only a VERIFY-scoped key and never a PROCESSOR key. The production verification tool is a pre-payment gate and fails closed, so misconfiguration blocks payments rather than allowing them. The v1 entry check is non-executable and does not itself authorize enforcement.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.mandateshield%2Fpayment-authority/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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=false; use the strict cryptographic tool for a production gate. Never send payment credentials or private keys.
Parametersamountrequiredlimitsnetworkpurposeagent_idrequiredasset_idprotocolrequiredresourcecreated_atexpires_atmandate_idrequiredintent_hash+7 more
normalize_agent_payment_protocol
Project Agent Payment Fields
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. X402 requires source-matched network+payTo identity and MPP requires source-matched HTTPS service-origin+method identity; merchant_id alone is insufficient. Evidence references are not independently verified. projection_fields_valid is not full protocol conformance: this tool never verifies delegated authority or a payment credential and always returns enforcement_authorized=false under assurance.
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 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 and freshly redeem the provider-bound permit before attempting an idempotent provider operation, then reconcile the outcome.
Parametersenveloperequiredevidencerequired
Version history
1
v1.13.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
