Index / MCP servers / SAAX Protocol

SAAX Protocol MCP server

Connect SAAX Protocol and your agent gets 26 tools, among them accept_commitment, cancel_commitment, close_commitment. It answers at https://saax-protocol.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 6 October 2026; the last check, on 22 November 2026, succeeded.

Status
Answering
Tools
26
Reliability
4 of 4 checks
Response time
287 ms
Transport
streamable HTTP
Last checked
22 November 2026

Durable commitment lifecycle, verification, governance and recovery layer for agentic commerce.

Description as the publisher wrote it.

The 26 tools SAAX Protocol offers

ToolWhat it does
accept_commitmentAccepts a signed preflight proposal with explicit buyer authorization and creates exactly ONE authenticated SAAX commitment. Revalidates the proposal (trusted provider key, profile version, expiry, combination, manifest digest), verifies th
Inputs: proposal, acceptance, idempotencyKey
cancel_commitmentCancels a commitment when the caller (verified by EIP-712 proof) holds buyer or authority authorization with cancel scope. Terminal and nonfinancial � no payment, refund, or settlement is executed. Reconciles authoritative state first. Idem
Inputs: commitmentId, agentId, role, proof, reason, idempotencyRef
close_commitmentCloses a fulfilled commitment (settled -> finalized) when the caller (verified by EIP-712 proof) holds system or authority authorization. Nonfinancial � no settlement, escrow release, or refund is executed. Reconciles authoritative state fi
Inputs: commitmentId, agentId, role, proof, idempotencyRef
create_commitmentCreates 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 prerequ
Inputs: buyerId, sellerId, terms, acceptanceCriteria, evidenceRequirements, recoveryPolicy
get_authority_validationValidates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.
Inputs: subscriptionEmail, proof, commitment
get_commitmentReturns 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.
Inputs: commitmentId
get_commitment_historyReturns the append-only lifecycle event ledger for a commitment � every recorded transition with actor, authority reference, state version, and evidence reference. The caller must present an EIP-712 authority proof binding its identity to t
Inputs: commitmentId, agentId, role, proof
get_commitment_statusReturns 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. Th
Inputs: commitmentId
get_evidence_verificationVerifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.
Inputs: subscriptionEmail, evidence, commitment, criterion
get_pending_actionsReturns the lifecycle actions the caller (verified by EIP-712 proof) may currently perform on a commitment � derived from the canonical transition map, the caller's role, and the caller's durable authorization scope. Read-only. For full rec
Inputs: commitmentId, agentId, role, proof
get_protocol_infoReturns 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_cap
get_recovery_statusReturns the authoritative commitment state, the caller's authorization status (active/revoked/expired), whether the commitment is recoverable, and the caller's permitted next actions. Reconciles the durable commitment row and the caller's a
Inputs: commitmentId, agentId, role, proof
get_routing_feeReturns 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.
get_supplier_detailsReturns the detailed record for one supplier in the SAAX Router index: identifier, name, description, services (name/endpoint/version), owner and source provenance. Call this after route_request or list_capabilities to inspect a specific su
Inputs: supplier_id
list_capabilitiesReturns 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
list_commitmentsReturns 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
Inputs: subscriptionEmail
list_disputesReturns the durable dispute records for a commitment (dispute identifiers, status, resolution, attribution, timestamps). The caller must present an EIP-712 authority proof and hold an active authorization on the commitment. Commitment-scope
Inputs: commitmentId, agentId, proof, status, limit, offset
list_evidenceReturns the durable evidence records for a commitment (stable identifiers, integrity references, submitter attribution, status, timestamps � never raw payload content). The caller must present an EIP-712 authority proof and hold an active a
Inputs: commitmentId, agentId, proof, status, limit, offset
pingReturns 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.
prepare_commitmentPrepares a free, NONBINDING signed proposal (preflight) for a desired SAAX capability. Validates capability, schema/version/digest, units, and the exact supported network/asset/rail/mode combination; returns a provider-signed proposal bindi
Inputs: profileVersion, capability, schema, units, financialProfile, constraints
raise_disputeRaises a durable dispute on a commitment and transitions it to the disputed state. The caller must present an EIP-712 authority proof and hold an unrevoked, unexpired authorization on the commitment (verified in-transaction). Disputes may o
Inputs: commitmentId, disputeId, agentId, proof, reason, evidenceRefs
resolve_disputeRecords an evaluator decision on an open dispute and transitions the commitment to the canonical nonfinancial outcome (continue|rework|satisfied|against). The caller must present an EIP-712 authority proof and hold an unrevoked, unexpired E
Inputs: disputeId, outcome, agentId, proof, reason, idempotencyRef
resume_commitmentLets an independently authorized replacement agent continue a commitment. Reconciles the authoritative state, verifies the caller's EIP-712 authority proof, and executes the requested nonfinancial transition through the canonical transition
Inputs: commitmentId, agentId, role, proof, action, idempotencyRef
route_requestSubmits 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 loo
Inputs: capability, budget, deadline
submit_evidenceDurably submits evidence for a commitment. The caller must present an EIP-712 authority proof; the recovered signer must hold an unrevoked, unexpired provider or buyer authorization on the commitment (verified in-transaction against the dur
Inputs: commitmentId, criterionId, agentId, proof, evidence, idempotencyRef
verify_evidenceSets the verification status of a submitted evidence record to verified or rejected. The caller must present an EIP-712 authority proof and hold an unrevoked, unexpired EVALUATOR authorization on the commitment (verified in-transaction). Id
Inputs: evidenceId, verdict, agentId, proof, reason, expectedVersion

Add SAAX Protocol to your AI client

Every block below points at https://saax-protocol.com/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http saax-protocol https://saax-protocol.com/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "saax-protocol": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://saax-protocol.com/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "saax-protocol": {
      "url": "https://saax-protocol.com/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "saax-protocol": {
      "type": "http",
      "url": "https://saax-protocol.com/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "saax-protocol": {
      "url": "https://saax-protocol.com/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "saax-protocol": {
      "serverUrl": "https://saax-protocol.com/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "saax-protocol": {
      "url": "https://saax-protocol.com/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: SAAX Protocol
version: 0.0.1
schema: v1
mcpServers:
  - name: SAAX Protocol
    type: streamable-http
    url: https://saax-protocol.com/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "saax-protocol": {
      "httpUrl": "https://saax-protocol.com/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "saax-protocol": {
      "type": "http",
      "url": "https://saax-protocol.com/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "saax-protocol": {
      "url": "https://saax-protocol.com/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fsaax-protocol.com%2Fmcp&type=streamable_http&id=saax-protocol&name=SAAX%20Protocol

Is SAAX Protocol up right now?

It answered our last check on 22 November 2026 in 287 ms. Over 4 checks since 6 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to SAAX Protocol

Questions about SAAX Protocol

How many tools does SAAX Protocol have?

26, as returned by the server's own tools/list on 22 November 2026: accept_commitment, cancel_commitment, close_commitment, create_commitment, get_authority_validation, get_commitment, get_commitment_history, get_commitment_status, and 18 more.

Is SAAX Protocol down?

It answered our last check on 22 November 2026 in 287 ms. Over 4 checks since 6 October 2026 it answered 4.

How do I add SAAX Protocol to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://saax-protocol.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does SAAX Protocol need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.bryantrudy24. Endpoint host: saax-protocol.com. ARD identifier: urn:air:io.github.bryantrudy24:mcp:saax-protocol. First indexed 5 October 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.