com.davisvillelabs/exitproof

Est-ce que com.davisvillelabs/exitproof est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.davisvillelabs/exitproof » 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 6 outils

• build_exit_pack≈ 1110 tokens

  Build a bounded cancellation/refund action pack from an existing actionable Exit Manifest. Pass manifest_id and access_token together as the credential pair returned by create_exit_manifest or settlement recovery; use get_exit_manifest for retrieval only, or check_reversibility then create_exit_manifest when no manifest exists. This $1.00 MPP operation prefers Tempo stablecoin when available, retains Stripe card/link as a compatible fallback, and can charge but never contacts the merchant, executes a cancellation, files a chargeback, or guarantees success. Invalid or mismatched credentials and non-actionable manifests are rejected before payment; an identical settled retry with the same payment credential avoids a second settlement, while generatedAt and deadlineStatus can reflect the current time.

  Paramètres, retour & exemple (2)

  Paramètres

  • manifest_id · string · requis
    Unguessable Exit Manifest identifier returned by create_exit_manifest. It starts with xm_ followed by 32 lowercase hexadecimal characters.
  • access_token · string · requis
    Secret bearer token returned by create_exit_manifest or deterministic settlement recovery. Required with manifest_id; treat it like a credential and do not log or expose it.

  Exemple d'appel

  {"name": "build_exit_pack", "arguments": {"manifest_id": "texte", "access_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"steps": [], "sources": [], "currency": "texte", "exitRoute": {}, "assessment": "texte", "manifestId": "texte", "generatedAt": "texte", "limitations": [], "actionability": {}, "prerequisites": [], "schemaVersion": "texte", "deadlineStatus": "open"}}

• check_agent_purchase≈ 2029 tokens

  Inspect one autonomous HTTP purchase before the calling agent pays it. This $0.01 machine-payment operation validates a real 402 challenge, compares advertised price/protocol/network/asset/payment destination when supplied, checks x402 v2 exact resource binding when available, and surfaces retry or settled-delivery recovery signals. ExitProof never forwards payment credentials and never sends a live POST, PUT, PATCH, or DELETE probe; for those methods the caller supplies an already-observed 402 challenge. Conflicting, malformed, inaccessible, non-402, or unsafe targets are rejected before ExitProof issues its own payment challenge. Use check_reversibility instead for cancellation/refund terms on a real-world commitment, create_exit_manifest to preserve an eligible exit path, and build_exit_pack when an exit is actually needed. A successful check is not a recommendation, merchant-identity guarantee, delivery guarantee, legal opinion, or authorization to spend.

  Paramètres, retour & exemple (7)

  Paramètres

  • operation · string · optionnel
    Optional caller label for the target operation. This is descriptive only and is included in the check digest.
  • advertised · object · optionnel
    Optional payment facts advertised by discovery metadata. ExitProof compares these to the observed 402 challenge and rejects material conflicts before its own payment challenge.
  • live_probe · boolean · optionnel
    Whether ExitProof may make one anonymous, credential-free request to target_url. Defaults true for GET/HEAD and false for state-changing methods.
  • target_url · string · requis
    Public HTTPS endpoint the agent is considering paying. Credentials, localhost, private-address literals, and non-HTTPS URLs are rejected.
  • request_method · string · optionnel · GET | HEAD | POST | PUT | PATCH | DELETE
    HTTP method of the contemplated purchase. Live probing is allowed only for GET or HEAD. For state-changing methods supply observed_response instead.
  • retry_contract · object · optionnel
    Optional retry, settled-delivery recovery, and refund/reversal facts advertised by the target. These remain caller-supplied unless independently verified elsewhere.
  • observed_response · object · optionnel
    A 402 response already observed by the calling agent. Required when live_probe is false. Supply payment challenge headers only, never a payment credential.

  Exemple d'appel

  {"name": "check_agent_purchase", "arguments": {"target_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"checks": [], "target": {}, "evidence": [], "nextStep": {}, "checkedAt": "texte", "advertised": "texte", "assessment": "eligible_to_attempt", "checkDigest": "texte", "limitations": [], "reversibility": {}, "schemaVersion": "texte", "observedPayment": {}}}

• check_reversibility≈ 2758 tokens

  Evaluate one commitment’s cancellation/refund reversibility from transaction-specific checkout terms plus maintained policy evidence, without charging or creating durable state. Use before a purchase, booking, subscription, rental, service, ticket, digital purchase, or deposit when exit deadlines or loss matter; use list_supported_policies only for maintained-overlay coverage, and create_exit_manifest only after paidExitManifestAvailable=true. Do not use for purchase desirability, legal advice, chargeback decisions, or executing a cancellation. Supply checkout_terms whenever available because they control the transaction-specific assessment; expected_commitment_at moves deadline evaluation forward when the commitment is future-dated, and missing or conflicting evidence can return assessment=unknown rather than inventing an exit right.

  Paramètres, retour & exemple (11)

  Paramètres

  • amount · number · requis
    Commitment amount in major currency units, for example 125.50 for USD 125.50. Must be non-negative and uses currency below for all monetary interpretation.
  • region · string · optionnel
    Optional state, province, or region label when the commitment or merchant terms are region-specific.
  • country · string · optionnel
    Optional two-letter ISO 3166-1 alpha-2 country code, such as US. Used to scope maintained policy rules when geography matters.
  • currency · string · optionnel
    Three-letter ISO 4217 currency code for amount and all monetary checkout terms. Defaults to USD.
  • merchant · string · requis
    Merchant, platform, provider, or counterparty name exactly enough to identify the commitment. Used to match maintained policy overlays; do not include account numbers, credentials, or secrets.
  • event_type · string · optionnel · initial | renewal | purchase | reservation | deposit | other
    Lifecycle event for this commitment. Use renewal for a recurring renewal, reservation for a booking event, deposit for a deposit event, or leave omitted for an initial commitment.
  • checkout_terms · object · optionnel
    Transaction-specific cancellation, refund, renewal, charge, and loss terms observed for this exact commitment. Supply these whenever available; they control the transaction-specific assessment while maintained policy evidence remains contextual.
  • commitment_type · string · requis · subscription | reservation | ticket | service | software | digital_purchase | rental | deposit
    Closest category for the commitment being evaluated. This affects policy matching and should describe what the user is committing to, not the payment method.
  • client_reference · string · optionnel
    Optional caller-owned correlation reference. ExitProof stores only a SHA-256 hash; do not place secrets or sensitive personal data here.
  • purchase_channel · string · optionnel · direct | apple | google_play | marketplace | travel_agency | other | unknown
    Where the commitment is being made or billed. Use apple or google_play when that billing platform controls cancellation/refund rules; use direct for the merchant itself.
  • expected_commitment_at · string · optionnel
    RFC 3339 timestamp with explicit timezone for when the commitment is expected to occur. ExitProof evaluates time windows at the later of now and this timestamp.

  Exemple d'appel

  {"name": "check_reversibility", "arguments": {"amount": 1, "merchant": "texte", "commitment_type": "subscription"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"reason": "texte", "currency": "texte", "evidence": [], "merchant": "texte", "assessment": "fully_reversible", "caseDigest": "texte", "amountMinor": 1, "evaluatedAt": "texte", "limitations": [], "evidenceBasis": "texte", "evidenceState": "texte", "schemaVersion": "texte"}}

• create_exit_manifest≈ 2060 tokens

  Persist a privacy-minimized Exit Manifest for an eligible commitment, then return its manifest_id and secret access_token. Use only after check_reversibility says paidExitManifestAvailable=true; pass the exact commitment facts to preserve, with transaction-specific checkout_terms controlling the assessment when supplied. Use check_reversibility for evaluation only, or get_exit_manifest when a manifest already exists. This state-changing $0.25 stablecoin MPP operation checks eligibility before any payment challenge; a fresh authorization creates durable state, while an identical settled retry with the same payment credential recovers the same manifest without a second settlement. The plaintext access token is returned to the caller but stored only as a SHA-256 hash.

  Paramètres, retour & exemple (11)

  Paramètres

  • amount · number · requis
    Commitment amount in major currency units, for example 125.50 for USD 125.50. Must be non-negative and uses currency below for all monetary interpretation.
  • region · string · optionnel
    Optional state, province, or region label when the commitment or merchant terms are region-specific.
  • country · string · optionnel
    Optional two-letter ISO 3166-1 alpha-2 country code, such as US. Used to scope maintained policy rules when geography matters.
  • currency · string · optionnel
    Three-letter ISO 4217 currency code for amount and all monetary checkout terms. Defaults to USD.
  • merchant · string · requis
    Merchant, platform, provider, or counterparty name exactly enough to identify the commitment. Used to match maintained policy overlays; do not include account numbers, credentials, or secrets.
  • event_type · string · optionnel · initial | renewal | purchase | reservation | deposit | other
    Lifecycle event for this commitment. Use renewal for a recurring renewal, reservation for a booking event, deposit for a deposit event, or leave omitted for an initial commitment.
  • checkout_terms · object · optionnel
    Transaction-specific cancellation, refund, renewal, charge, and loss terms observed for this exact commitment. Supply these whenever available; they control the transaction-specific assessment while maintained policy evidence remains contextual.
  • commitment_type · string · requis · subscription | reservation | ticket | service | software | digital_purchase | rental | deposit
    Closest category for the commitment being evaluated. This affects policy matching and should describe what the user is committing to, not the payment method.
  • client_reference · string · optionnel
    Optional caller-owned correlation reference. ExitProof stores only a SHA-256 hash; do not place secrets or sensitive personal data here.
  • purchase_channel · string · optionnel · direct | apple | google_play | marketplace | travel_agency | other | unknown
    Where the commitment is being made or billed. Use apple or google_play when that billing platform controls cancellation/refund rules; use direct for the merchant itself.
  • expected_commitment_at · string · optionnel
    RFC 3339 timestamp with explicit timezone for when the commitment is expected to occur. ExitProof evaluates time windows at the later of now and this timestamp.

  Exemple d'appel

  {"name": "create_exit_manifest", "arguments": {"amount": 1, "merchant": "texte", "commitment_type": "subscription"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"createdAt": "texte", "expiresAt": "texte", "assessment": "texte", "manifestId": "texte", "accessToken": "texte", "privacyNote": "texte", "paidExitPackAvailable": true, "accessTokenReturnedOnce": true, "accessTokenReissuedForSettlementRecovery": true}}

• get_exit_manifest≈ 509 tokens

  Retrieve one previously created Exit Manifest without charging or changing stored state. Pass manifest_id and access_token together: the ID selects the record and the secret token authorizes access to that same record, so neither value is sufficient alone. Use this for preserved evidence and terms; use build_exit_pack for an actionable cancellation/refund plan, or create_exit_manifest when no manifest exists. This free, repeatable read does not refresh, re-evaluate, or extend evidence; missing, expired, or mismatched credentials fail without modifying the manifest.

  Paramètres, retour & exemple (2)

  Paramètres

  • manifest_id · string · requis
    Unguessable Exit Manifest identifier returned by create_exit_manifest. It starts with xm_ followed by 32 lowercase hexadecimal characters.
  • access_token · string · requis
    Secret bearer token returned by create_exit_manifest or deterministic settlement recovery. Required with manifest_id; treat it like a credential and do not log or expose it.

  Exemple d'appel

  {"name": "get_exit_manifest", "arguments": {"manifest_id": "texte", "access_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"manifest": {}, "schemaVersion": "texte"}}

• list_supported_policies≈ 591 tokens

  List the maintained merchant policy overlays and snapshot version/date ExitProof can add to transaction-specific evidence. Use this only to inspect maintained coverage; use check_reversibility to evaluate an actual commitment, including an unlisted merchant when transaction-specific checkout_terms are available. An absent merchant means no maintained overlay, not that no cancellation, refund, contractual, or legal right exists. This is a free read-only snapshot: it creates no durable state, issues no payment challenge, and does not fetch or verify a merchant’s live policy at call time.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_supported_policies", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"important": "texte", "merchants": [], "schemaVersion": "texte", "policySnapshot": {}}}

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://exitproof.davisvillelabs.com/mcp