SAAX Protocol
Durable commitment lifecycle, verification, governance and recovery layer for agentic commerce
Reviews
No review yet. Used SAAX Protocol? Be the first to help others choose.What it does
SAAX Protocol is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 10h ago (live check)Hosted endpoint
https://saax-protocol.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http saax-protocol https://saax-protocol.com/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"saax-protocol": {
"url": "https://saax-protocol.com/mcp"
}
}
}Reliability
Re-tested about every 3 days · last check 10h agoObserved endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 19 Oct 2026). How we measure
Tool changes
Tool tracking since 13 Nov 2026 · test history since 19 Oct 2026+13 added · 26 tools in the latest list
- 17 Nov 2026+ added
cancel_commitmentfirst listed - 17 Nov 2026+ added
close_commitmentfirst listed - 17 Nov 2026+ added
get_commitment_historyfirst listed - 17 Nov 2026+ added
get_pending_actionsfirst listed - 17 Nov 2026+ added
get_recovery_statusfirst listed - 17 Nov 2026+ added
get_supplier_detailsfirst listed - 17 Nov 2026+ added
list_disputesfirst listed - 17 Nov 2026+ added
list_evidencefirst listed - 17 Nov 2026+ added
raise_disputefirst listed - 17 Nov 2026+ added
resolve_disputefirst listed - 17 Nov 2026+ added
resume_commitmentfirst listed - 17 Nov 2026+ added
submit_evidencefirst listed - 17 Nov 2026+ added
verify_evidencefirst listed
Changes are confirmed by comparing complete tool lists only, read about every 3 days, and dated by the day we saw them. A renamed tool appears as one removal and one addition.
Live check
Electra Index connected to the hosted endpoint 10h agoONLINE SAAX Protocol answered an MCP connection on 21 Nov 2026 and introduced itself as saax-protocol 1.0.3 (MCP protocol 2025-06-18).
26 tools offered to AI assistants
get_protocol_info· 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_capget_routing_fee· 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.ping· 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.route_request· 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 looget_commitment· 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.list_capabilities· 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_protocollist_commitments· 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 checksget_commitment_status· 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. Thcreate_commitment· 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 prerequget_evidence_verification· Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.get_authority_validation· Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.get_commitment_history· Returns 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
Show 14 more
get_recovery_status· Returns 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 aget_pending_actions· Returns 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 recresume_commitment· Lets 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 transitioncancel_commitment· Cancels 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. Idemclose_commitment· Closes 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 fiprepare_commitment· Prepares 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 bindiaccept_commitment· Accepts 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 thsubmit_evidence· Durably 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 durlist_evidence· Returns 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 averify_evidence· Sets 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). Idraise_dispute· Raises 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 oresolve_dispute· Records 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 Elist_disputes· Returns 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-scopeget_supplier_details· Returns 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
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://saax-protocol.com/mcp | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Website | https://saax-protocol.com | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Version | 1.0.4 | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Repository | https://github.com/bryantrudy24/saax-protocol | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
Change history
- VERSION14 Nov 20261.0.3 → 1.0.4
- VERSION06 Oct 20261.0.2 → 1.0.3
- VERSION05 Oct 20261.0.1 → 1.0.2
- VERSION05 Oct 20261.0.0 → 1.0.1
- NEW05 Oct 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is SAAX Protocol still online?
Free alerts · no account▲ 0Do you run SAAX Protocol? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about SAAX Protocol
How do I connect SAAX Protocol?
Use the hosted endpoint https://saax-protocol.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does SAAX Protocol offer?
When Electra Index connected on 21 Nov 2026, it listed 26 tools: get_protocol_info, get_routing_fee, ping, route_request, get_commitment, list_capabilities, list_commitments, get_commitment_status and more. The full list is in "Live check" above.
Is SAAX Protocol online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 10h ago.