MandateShield AI Payment Evidence MCP Server

com.mandateshield/payment-authority

answering

MandateShield AI Payment Evidence is answering right now. Last checked 10 min ago. It exposes 3 tools.

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

Uptime history 41 hours of history

41 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1108 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.payment-authority]
url = "https://mandateshield.com/api/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

normalize

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. 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.

payment

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=false; use the strict cryptographic tool for a production gate. Never send payment credentials or private keys.

verify

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 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.

Endpoints

URL	Transport	State	Latency	Checked
https://mandateshield.com/api/mcp	streamable-http	answering	1641 ms	10 min ago

MandateShield AI Payment Evidence — questions

Answers built from our own checks of this server.

What can MandateShield AI Payment Evidence do?

It exposes 3 tools, read directly from the server on our last check. Among them: check_ai_payment_authority, normalize_agent_payment_protocol, verify_cryptographic_payment_authority. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is MandateShield AI Payment Evidence working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1108 ms. The bar chart above shows every period we have measured.

How do I connect MandateShield AI Payment Evidence?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does MandateShield AI Payment Evidence need an API key?

No. MandateShield AI Payment Evidence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is MandateShield AI Payment Evidence?

It answers our handshake in 1108 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.