Combien d'outils expose io.github.grupoanesthy-spec/agent-transaction-trust ?

io.github.grupoanesthy-spec/agent-transaction-trust expose 6 outil(s). Le coût de contexte pour les charger tous est d'environ 1965 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / IA & Mémoire / io.github.grupoanesthy-spec/agent-transaction-trust

io.github.grupoanesthy-spec/agent-transaction-trust

serveur MCP (Model Context Protocol) · agent-transaction-trust 1.0.0

▸ IA & Mémoire

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

directAccès

~1965 tokensCoût de contexte

6Outils

Est-ce que io.github.grupoanesthy-spec/agent-transaction-trust est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.grupoanesthy-spec/agent-transaction-trust » 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

authorize_x402_ap2≈ 724 tokens
Paid pre-payment trust gate. Use after create_ap2_challenge and after receiving the merchant's real x402 PAYMENT-REQUIRED challenge, but before paying the merchant. Verifies AP2 v0.2 authority and binds approval to the exact merchant challenge and HTTP request. On approval returns authorization_token; next pay the merchant, then call verify_settlement. Machine price: $0.001 via x402. If authorization is denied, the Trust fee is not settled/charged.
Paramètres, retour & exemple (7)
Paramètres
- nonce · string · optionnel
  Optional caller nonce for correlation; do not reuse across distinct purchase attempts.
- payer · string · requis
  Base payer wallet address that will authorize the merchant x402 payment.
- request · object · requis
  Exact HTTP request the agent intends to execute after approval; changing it invalidates the authorization binding.
- category · string · requis
  Service/purchase category evaluated against the AP2 mandate constraints, for example ai-infrastructure.
- merchant_id · string · requis
  Stable identifier for the merchant/resource being authorized.
- ap2_authority · object · requis
  AP2 authority proof for this exact purchase attempt.
- payment_required · ? · requis
  Merchant's real x402 PAYMENT-REQUIRED payload, either as the decoded object or the original encoded/string form.
Exemple d'appel
```
{"name": "authorize_x402_ap2", "arguments": {"payer": "texte", "request": {}, "category": "texte", "merchant_id": "texte", "ap2_authority": {}, "payment_required": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
clearance_x402_ap2≈ 620 tokens
Paid transaction-clearance decision for an autonomous x402 purchase. Use after create_ap2_challenge and after receiving the merchant's real PAYMENT-REQUIRED challenge, but before paying the merchant. Verifies AP2 v0.2 authority, exact request/challenge integrity, and public merchant-risk evidence. Returns clearance_decision APPROVED, REVIEW or DENIED and a signed clearance_token. APPROVED may proceed automatically; REVIEW should not auto-pay; DENIED should not pay. Machine price: $0.001 via x402.
Paramètres, retour & exemple (7)
Paramètres
- nonce · string · optionnel
- payer · string · requis
  Base payer wallet address that would pay the merchant.
- request · object · requis
  Exact HTTP request the agent intends to execute if clearance permits it.
- category · string · requis
  Service/purchase category for the transaction.
- merchant_id · string · requis
  Stable merchant identifier covered by the AP2 authority.
- ap2_authority · object · requis
- payment_required · ? · requis
  Merchant's real x402 PAYMENT-REQUIRED payload, decoded or encoded.
Exemple d'appel
```
{"name": "clearance_x402_ap2", "arguments": {"payer": "texte", "request": {}, "category": "texte", "merchant_id": "texte", "ap2_authority": {}, "payment_required": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
create_ap2_challenge≈ 168 tokens
Free prerequisite for AP2-native transaction clearance or authorization. Call before clearance_x402_ap2 or authorize_x402_ap2, bind the returned challenge into the AP2 Payment Mandate proof, then pass that challenge token as ap2_authority.challenge_token. The challenge is short-lived and intended for one purchase flow.
Paramètres, retour & exemple (1)
Paramètres
- ttl_seconds · integer · optionnel
  Challenge lifetime in seconds. Optional; must be 30-300 seconds when provided.
Exemple d'appel
```
{"name": "create_ap2_challenge", "arguments": {"ttl_seconds": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_trust_manifest≈ 113 tokens
Free, read-only entry point. Call this first when deciding whether Agent Transaction Trust fits an x402 purchase. Returns capabilities, supported authority modes, proof key, price/network information, and the endpoints needed for transaction clearance, authorization, and settlement verification.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "get_trust_manifest", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
verify_settlement≈ 268 tokens
Free post-payment step. Call only after the merchant x402 payment for a previously approved authorization or transaction clearance. Verifies the Base USDC settlement on-chain and, when it matches the authorization, returns a signed settlement receipt. The authorization_token may come from clearance_x402_ap2 or authorize_x402_ap2; payment_response is the merchant x402 PAYMENT-RESPONSE when available. No additional Trust fee is charged.
Paramètres, retour & exemple (2)
Paramètres
- payment_response · string · optionnel
  Optional merchant x402 PAYMENT-RESPONSE header/value from the completed payment; omit only when on-chain reconciliation can identify the settlement.
- authorization_token · string · requis
  Signed authorization_token returned by clearance_x402_ap2 or authorize_x402_ap2 for the exact merchant request.
Exemple d'appel
```
{"name": "verify_settlement", "arguments": {"authorization_token": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
verify_trust_token≈ 151 tokens
Free, read-only token check. Use this to validate the signature and expiry of a Trust policy, authorization token, transaction clearance token, or settlement receipt; it does not perform on-chain settlement verification.
Paramètres, retour & exemple (1)
Paramètres
- token · string · requis
  Signed Trust token returned by policy issuance, authorization, transaction clearance, or settlement verification.
Exemple d'appel
```
{"name": "verify_trust_token", "arguments": {"token": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```

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://json-repair-api-9ybv.onrender.com/mcp