accueil / serveurs / Dev & Code / io.github.bryantrudy24/saax-protocol
io.github.bryantrudy24/saax-protocol
serveur MCP (Model Context Protocol) · saax-protocol 1.0.3
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.bryantrudy24/saax-protocol est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.bryantrudy24/saax-protocol » 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 11 outils
- create_commitment≈ 607 tokens
Creates a governed commitment between a buyer and a seller and persists it to the SAAX commitment store. The commitment is settlement-rail-neutral: settlementRail is metadata only (x402, mpp, ap2, acp, or unspecified) and is NEVER a prerequisite. Returns the new commitment id (saax_<hash>), createdAt, status, and the settlementRail. Call this BEFORE any payment flow to establish the governed commitment record. Once created, use get_commitment to read the manifest.
Paramètres, retour & exemple (7)
Paramètresterms· object · requis
The commercial terms: deliverable, price, deadlinebuyerId· string · requis
The buyer's identity: 0x-address or agent idsellerId· string · requis
The seller's identity: 0x-address or agent idrecoveryPolicy· object · optionnel
Recovery policy on failuresettlementRail· string · optionnel · x402 | mpp | ap2 | acp | unspecified
The settlement rail as metadata. Never a prerequisite; 'unspecified' is valid.acceptanceCriteria· array · requis
Objective acceptance criteria for fulfillmentevidenceRequirements· array · optionnel
Evidence the seller must supply
Exemple d'appel{"name": "create_commitment", "arguments": {"terms": {}, "buyerId": "texte", "sellerId": "texte", "acceptanceCriteria": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_authority_validation≈ 201 tokens
Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.
Paramètres, retour & exemple (3)
Paramètresproof· ? · requis
The AuthorityProof object (proofType, issuer, subject, scope, validFrom, validUntil, signature, verificationScheme, verificationMaterial)commitment· ? · requis
The commitment or requested action the proof must authorizesubscriptionEmail· string · requis
The subscription email (must have an active SAAX Premium subscription)
Exemple d'appel{"name": "get_authority_validation", "arguments": {"proof": "texte", "commitment": "texte", "subscriptionEmail": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_commitment≈ 160 tokens
Returns the full commitment object for a given commitment ID — including terms, state, manifest hash, and evidence references. Call this when an agent needs the complete commitment record. For status-only polling, use get_commitment_status. For listing all commitments for a subscriber, use list_commitments.
Paramètres, retour & exemple (1)
ParamètrescommitmentId· string · requis
The commitment id (0x-prefixed or agent-id style) to look up
Exemple d'appel{"name": "get_commitment", "arguments": {"commitmentId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_commitment_status≈ 174 tokens
Returns only the current lifecycle state for a given commitment ID, plus the recommended next action for the calling agent. Call this before retrying any commitment that timed out — an unknown outcome is a status check, not another POST. The next_action field tells the agent whether to retry, poll, or stop. For the full commitment record, use get_commitment.
Paramètres, retour & exemple (1)
ParamètrescommitmentId· string · requis
The commitment id to poll for its lifecycle state
Exemple d'appel{"name": "get_commitment_status", "arguments": {"commitmentId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_evidence_verification≈ 237 tokens
Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.
Paramètres, retour & exemple (4)
Paramètresevidence· ? · requis
The evidence object (evidenceId, evidenceType, issuer, subject, payload, payloadHash, signature, verificationScheme, commitmentId, acceptanceCriterionId, ...)criterion· ? · requis
The verification policy / acceptance criterioncommitment· ? · requis
The commitment object the evidence binds tosubscriptionEmail· string · requis
The subscription email (must have an active SAAX Premium subscription)
Exemple d'appel{"name": "get_evidence_verification", "arguments": {"evidence": "texte", "criterion": "texte", "commitment": "texte", "subscriptionEmail": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_protocol_info≈ 120 tokens
Returns the SAAX Protocol version, available capability count, and the URL to the specification. Call this when an agent needs a one-time overview of the protocol. For pricing, use get_routing_fee. For the full capability list, use list_capabilities. For a liveness check, use ping.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_protocol_info", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_routing_fee≈ 100 tokens
Returns the current routing fee schedule. Call this before initiating a routing request to determine the expected cost. For capability discovery, use list_capabilities. For protocol overview, use get_protocol_info.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_routing_fee", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_capabilities≈ 110 tokens
Returns the capabilities currently indexed by the SAAX Router, with supplier counts per capability. Call this to discover what can be routed. For pricing of a specific capability, use get_routing_fee. For protocol overview, use get_protocol_info.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_capabilities", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_commitments≈ 158 tokens
Returns all commitments associated with a subscription email. Requires an active SAAX Premium subscription. Call this to retrieve commitment history for a subscriber. For a single commitment by ID, use get_commitment. For status-only checks, use get_commitment_status.
Paramètres, retour & exemple (1)
ParamètressubscriptionEmail· string · requis
The subscription email (must have an active SAAX Premium subscription)
Exemple d'appel{"name": "list_commitments", "arguments": {"subscriptionEmail": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - ping≈ 94 tokens
Returns a lightweight liveness response. Call this to verify the endpoint is reachable. Do not use for discovery, capability listing, or pricing — use get_protocol_info, list_capabilities, or get_routing_fee instead.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "ping", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - route_request≈ 196 tokens
Submits a capability request and returns ranked supplier matches. Commitment creation with payment runs through the HTTP POST /route endpoint, not this tool. Use list_capabilities first to discover available capabilities. For commitment lookup after routing, use get_commitment.
Paramètres, retour & exemple (3)
Paramètresbudget· number · optionnel
Maximum budget in USDC the buyer will paydeadline· number · optionnel
Deadline in seconds from now for deliverycapability· string · requis
The capability demanded, e.g. 'security scan'
Exemple d'appel{"name": "route_request", "arguments": {"capability": "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é ».