com.mandateshield/payment-authority

Est-ce que com.mandateshield/payment-authority est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.mandateshield/payment-authority » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 3 outils

• check_ai_payment_authority≈ 2584 tokens

  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.

  Paramètres, retour & exemple (19)

  Paramètres

  • amount · object · requis
  • limits · object · optionnel
    Sandbox analysis policy. Live v2 ignores caller policy and loads the registered mandate.
  • network · string · optionnel
    Exact network or chain identifier; required for atomic X402 payments.
  • purpose · string · optionnel
    Non-sensitive plain-language purchase purpose.
  • agent_id · string · requis
    Stable identifier for the acting AI agent.
  • asset_id · string · optionnel
    Exact token or asset identifier; required for atomic X402 payments.
  • protocol · string · requis · AP2 | TAP | UCP | X402 | MPP | ACP | CUSTOM
    Source protocol or CUSTOM for a normalized envelope.
  • resource · string · optionnel
    Exact paid resource identifier; required for atomic X402 payments.
  • created_at · string · optionnel
  • expires_at · string · optionnel
  • mandate_id · string · requis
    Stable identifier for the user-approved authority.
  • intent_hash · string · optionnel
  • merchant_id · string · requis
    Stable identifier for the final seller or payee.
  • http_request · object · optionnel
    Optional signed HTTP action projection used by the narrow first-party x402 v2 exact/EIP-3009 Gate adapter.
  • user_consent · boolean · optionnel
  • checkout_hash · string · optionnel
    Digest or stable identifier for the exact final checkout.
  • payee_identity · object · optionnel
    Versioned canonical payee identity bound into the signed purchase envelope. The model records exact provider identifiers and verification evidence; it does not independently validate an external registry, TLS session, provider account or domain-control document.
  • idempotency_key · string · requis
    Unique identifier for this intended payment attempt.
  • credential_binding · string · optionnel

  Exemple d'appel

  {"name": "check_ai_payment_authority", "arguments": {"amount": {}, "agent_id": "texte", "protocol": "AP2", "mandate_id": "texte", "merchant_id": "texte", "idempotency_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"mode": "texte", "risk": {}, "error": "texte", "score": 1, "receipt": "texte", "controls": {}, "decision": "ALLOW", "findings": [], "protocol": "texte", "persisted": true, "checked_at": "texte", "recommended_action": "texte"}}

• normalize_agent_payment_protocol≈ 3925 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • source · ? · requis
    Raw protocol input: AP2 compact SD-JWT, x402 PAYMENT-REQUIRED base64 JSON, MPP WWW-Authenticate Payment challenge, or the documented decoded object.
  • adapter · string · requis · AP2_CLOSED_PAYMENT_SD_JWT | X402_V2_PAYMENT_REQUIRED | MPP_HTTP_PAYMENT_CHALLENGE
  • context · object · requis
  • selection · object · optionnel

  Exemple d'appel

  {"name": "normalize_agent_payment_protocol", "arguments": {"source": "texte", "adapter": "AP2_CLOSED_PAYMENT_SD_JWT", "context": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"adapter": "texte", "envelope": {}, "protocol": "AP2", "warnings": [], "assurance": {}, "next_step": "texte", "source_digest": "texte", "adapter_version": "texte", "envelope_digest": "texte"}}

• verify_cryptographic_payment_authority≈ 3104 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • envelope · object · requis
  • evidence · object · requis

  Exemple d'appel

  {"name": "verify_cryptographic_payment_authority", "arguments": {"envelope": {}, "evidence": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"mode": "texte", "risk": {}, "error": "texte", "score": 1, "receipt": "texte", "controls": {}, "decision": "ALLOW", "findings": [], "protocol": "texte", "assurance": {}, "persisted": true, "checked_at": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mandateshield.com/api/mcp