# SAAX Protocol MCP server

> Create and manage durable commitment records for agentic commerce, with evidence verification, disputes and recovery by replacement agents.

- Listing: https://mcp.tc/i/saax-protocol
- Connect: use the server's own URL `https://saax-protocol.com/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Finance & Payments](https://mcp.tc/c/finance-payments)
- Vendor: SAAX Protocol
- Homepage: <https://saax-protocol.com/>

## About

SAAX Protocol is a vendor-neutral commitment lifecycle layer for agentic commerce. Its tools discover routable capabilities and suppliers, prepare signed nonbinding proposals, accept them into commitments, submit and verify evidence, raise and resolve disputes, and let an independently authorized agent resume a commitment after the original worker stops.

The server runs as a hosted streamable HTTP endpoint at saax-protocol.com/mcp. Read-only discovery tools work without sign-in or an API key. Lifecycle actions require an EIP-712 authority proof, and a few tools require an active SAAX Premium subscription. The vendor labels live mainnet payments as public beta and escrow custody as testnet-only.

## What it can do

- Discover routed capabilities and ranked suppliers
- Prepare free, signed, nonbinding proposals
- Accept proposals to create authenticated commitments
- Read commitment state, history and recovery status
- Submit, list and verify fulfillment evidence
- Raise, list and resolve disputes without financial transfer
- Resume, cancel or close commitments with an authority proof

## Tools (26)

- `get_protocol_info`: Return protocol version, capability count and specification URL.
- `get_routing_fee`: Return the current routing fee schedule.
- `ping`: Lightweight liveness check.
- `route_request`: Submit a capability request and get ranked supplier matches.
- `get_commitment`: Return the full commitment record by ID.
- `list_capabilities`: List indexed capabilities with supplier counts.
- `list_commitments`: List commitments for a subscription email (Premium).
- `get_commitment_status`: Return lifecycle state and recommended next action.
- `create_commitment`: Create a rail-neutral commitment between buyer and seller.
- `get_evidence_verification`: Verify evidence against acceptance criteria (Premium).
- `get_authority_validation`: Validate an authority proof against a commitment (Premium).
- `get_commitment_history`: Return the append-only lifecycle journal for a commitment.
- `get_recovery_status`: Return state, caller authorization and permitted recovery actions.
- `get_pending_actions`: Return lifecycle actions the caller may perform now.
- `resume_commitment`: Let an authorized replacement agent continue a commitment.
- `cancel_commitment`: Cancel a commitment without any financial action.
- `close_commitment`: Close a fulfilled commitment from settled to finalized.
- `prepare_commitment`: Prepare a free, nonbinding signed proposal.
- `accept_commitment`: Accept a signed proposal and create one authenticated commitment.
- `submit_evidence`: Submit fulfillment evidence for a commitment.
- `list_evidence`: List evidence records for a commitment.
- `verify_evidence`: Mark a submitted evidence record verified or rejected.
- `raise_dispute`: Raise a dispute and move the commitment to disputed.
- `resolve_dispute`: Record an evaluator decision on an open dispute.
- `list_disputes`: List dispute records for a commitment.
- `get_supplier_details`: Return the detailed record for one indexed supplier.

## Example prompts

- "List the capabilities currently routable through SAAX."
- "Check the status of commitment saax\_abc123 and tell me the next action."
- "Prepare a signed proposal for a data-extraction capability."
- "Show the recovery status for this commitment so a replacement agent can continue."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

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

2. Start Claude Code and type `/mcp`. **saax-protocol** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **SAAX Protocol** and paste this URL:

```url
https://saax-protocol.com/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=SAAX%20Protocol&connectorUrl=https%3A%2F%2Fsaax-protocol.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://saax-protocol.com/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://saax-protocol.com/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=saax-protocol&config=eyJ1cmwiOiJodHRwczovL3NhYXgtcHJvdG9jb2wuY29tL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=saax-protocol&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fsaax-protocol.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"saax-protocol","type":"http","url":"https://saax-protocol.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

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

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "saax-protocol": {
      "serverUrl": "https://saax-protocol.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add saax-protocol --url https://saax-protocol.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

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

### Gemini CLI

```bash
gemini mcp add --transport http saax-protocol https://saax-protocol.com/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "saax-protocol": {
      "type": "http",
      "url": "https://saax-protocol.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://saax-protocol.com/mcp`.

## Details

- Server version: 1.0.3
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-15 (reachable)
- Listed: 2026-11-15
- Updated: 2026-11-15

---
Source: https://mcp.tc/i/saax-protocol (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report