SAAX Protocol MCP Server

by bryantrudy24 Your server? Claim it

not responding

SAAX Protocol is listed as active in the registry but did not answer our last check. It exposes 11 tools.

Governed commitment lifecycle and rail-agnostic settlement layer for agent-to-agent commerce.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 35 days of history · worst day 0%

35 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

119 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 15

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 October 2026. No other catalogue keeps this.

14 Oct 8 tool descriptions were rewritten get_authority_validation, get_commitment, get_evidence_verification and 5 more

14 Oct 3 tools appeared create_commitment, get_commitment_status, list_commitments

7 Oct 2 tools appeared get_authority_validation, get_evidence_verification

7 Oct 2 tools changed the parameters they ask for get_authority_validation, get_evidence_verification

SAAX Protocol does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add saax-protocol --transport http https://www.saax-protocol.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://www.saax-protocol.com/mcp

~/.codex/config.toml

[mcp_servers.saax-protocol]
url = "https://www.saax-protocol.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "saax-protocol": {
      "url": "https://www.saax-protocol.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "saax-protocol": {
      "type": "http",
      "url": "https://www.saax-protocol.com/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

commitment

create_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 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.

get_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. For listing all commitments for a subscriber, use list_commitments.

get_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. The next_action field tells the agent whether to retry, poll, or stop. For the full commitment record, use get_commitment.

authority

get_authority_validation

Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.

capabilities

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_protocol_info.

commitments

list_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 checks, use get_commitment_status.

evidence

get_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.

ping

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.

protocol

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_capabilities. For a liveness check, use ping.

route

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 lookup after routing, use get_commitment.

routing

get_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.

Endpoints

URL	Transport	State	Latency	Checked
https://www.saax-protocol.com/mcp	streamable-http	answering	119 ms	0 min ago

Alternatives to SAAX Protocol

same job, measured the same way

Junto MCP

by vrllrv

The payment protocol for people and agents. One MCP server, any payment rail.

52 installs/wk local only

Ophir

by ophir-ai-creator

Ophir protocol tools for AI agent discovery, negotiation, and settlement

58 installs/wk local only

Agentic Commerce

by bosonprotocol

MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.

63 tools answering

Agoragentic Agent OS MCP

by rhein1

Triptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.

1 157 installs/wk 17 tools answering

Xap

by omoshola-o

Agent settlement protocol — discover, negotiate, settle, and verify with XAP.

60 installs/wk local only

Pyrimid Protocol

by pyrimid

Agent-commerce MCP server for x402/USDC payments and affiliate splits on Base.

7 tools answering

Commerce Context Layer

by vviinn

Context layer with semantic and visual search and discovery for agentic commerce — by vviinn.

answering

Acp Sandbox

by flo-voice1

Agentic Commerce Protocol sandbox: agent builds a cart, human approves a real PayPal payment.

8 tools answering

SAAX Protocol — questions

Answers built from our own checks of this server.

What can SAAX Protocol do?

It exposes 11 tools, read directly from the server on our last check. Among them: create_commitment, get_authority_validation, get_commitment, get_commitment_status, get_evidence_verification, get_protocol_info and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is SAAX Protocol working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 119 ms. The bar chart above shows every period we have measured.

Is SAAX Protocol still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists SAAX Protocol as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect SAAX Protocol?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does SAAX Protocol need an API key?

No. SAAX Protocol completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.