# SAAX Protocol (remote · www.saax-protocol.com)

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

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.saax-protocol.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/bryantrudy24-saax-protocol/www.md), [page](https://verifymcp.io/servers/bryantrudy24-saax-protocol/www)

## Channel facts

- Endpoint: `https://www.saax-protocol.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1054 tokens (~95/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SAAX Protocol MCP server?

SAAX Protocol is a hosted endpoint at https://www.saax-protocol.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bryantrudy24-saax-protocol": {
      "type": "remote",
      "url": "https://www.saax-protocol.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bryantrudy24-saax-protocol --url 'https://www.saax-protocol.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bryantrudy24-saax-protocol:
    url: "https://www.saax-protocol.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "bryantrudy24-saax-protocol": {
      "Transport": "http",
      "Url": "https://www.saax-protocol.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bryantrudy24-saax-protocol -t streamable-http -u 'https://www.saax-protocol.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `get_protocol_info` (~70 tokens)

Get SAAX Protocol information

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.

### `get_routing_fee` (~48 tokens)

Get SAAX 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` (~51 tokens)

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` (~104 tokens)

Route a demand to ranked suppliers

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.

Input parameters:

- `budget` (number): Maximum budget in USDC the buyer will pay
- `capability` (string, required): The capability demanded, e.g. 'security scan'
- `deadline` (number): Deadline in seconds from now for delivery

### `get_commitment` (~91 tokens)

Get a commitment manifest

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.

Input parameters:

- `commitmentId` (string, required): The commitment id (0x-prefixed or agent-id style) to look up

### `list_capabilities` (~57 tokens)

List routed 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.

### `list_commitments` (~79 tokens)

List commitments for a subscriber

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.

Input parameters:

- `subscriptionEmail` (string, required): The subscription email (must have an active SAAX Premium subscription)

### `get_commitment_status` (~99 tokens)

Get a commitment's lifecycle state

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.

Input parameters:

- `commitmentId` (string, required): The commitment id to poll for its lifecycle state

### `create_commitment` (~230 tokens)

Create a rail-neutral 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.

Input parameters:

- `acceptanceCriteria` (array, required): Objective acceptance criteria for fulfillment
- `buyerId` (string, required): The buyer's identity: 0x-address or agent id
- `evidenceRequirements` (array): Evidence the seller must supply
- `recoveryPolicy` (object): Recovery policy on failure
- `sellerId` (string, required): The seller's identity: 0x-address or agent id
- `settlementRail` (string): The settlement rail as metadata. Never a prerequisite; 'unspecified' is valid.
- `terms` (object, required): The commercial terms: deliverable, price, deadline

### `get_evidence_verification` (~121 tokens)

Verify evidence against acceptance criteria

Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.

Input parameters:

- `commitment` (required): The commitment object the evidence binds to
- `criterion` (required): The verification policy / acceptance criterion
- `evidence` (required): The evidence object (evidenceId, evidenceType, issuer, subject, payload, payloadHash, signature, verificationScheme, commitmentId, acceptanceCriterionId, ...)
- `subscriptionEmail` (string, required): The subscription email (must have an active SAAX Premium subscription)

### `get_authority_validation` (~104 tokens)

Validate an authority proof

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

Input parameters:

- `commitment` (required): The commitment or requested action the proof must authorize
- `proof` (required): The AuthorityProof object (proofType, issuer, subject, scope, validFrom, validUntil, signature, verificationScheme, verificationMaterial)
- `subscriptionEmail` (string, required): The subscription email (must have an active SAAX Premium subscription)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bryantrudy24-saax-protocol/www#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 71
- 2026-10-12: 61
- 2026-10-10: 70
- 2026-10-07: 67

## Common questions

### What is the SAAX Protocol MCP server?

SAAX Protocol is an MCP server listed in the public MCP registry as io.github.bryantrudy24/saax-protocol. Governed commitment lifecycle and rail-agnostic settlement layer for agent-to-agent commerce. This page covers its hosted endpoint (https://www.saax-protocol.com/mcp).

### Is the SAAX Protocol MCP server safe to use?

SAAX Protocol scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SAAX Protocol MCP server expose?

SAAX Protocol exposes 11 tools: get_protocol_info, get_routing_fee, ping, route_request, get_commitment, and 6 more. Their descriptions and schemas cost roughly 1,054 tokens of context every time the server is loaded.

### Does the SAAX Protocol MCP server require authentication?

No. We connected to SAAX Protocol without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SAAX Protocol MCP server still maintained?

SAAX Protocol is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SAAX Protocol MCP server?

VerifyMCP ran 12 checks on SAAX Protocol, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SAAX Protocol: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.saax-protocol.com/mcp
- Repository: https://github.com/bryantrudy24/saax-protocol
- Changelog RSS feed: https://verifymcp.io/servers/bryantrudy24-saax-protocol/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/bryantrudy24-saax-protocol/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/bryantrudy24-saax-protocol/www.json
- HTML version of this page: https://verifymcp.io/servers/bryantrudy24-saax-protocol/www