# SAAX Protocol

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

- name: io.github.bryantrudy24/saax-protocol
- version: 1.0.3
- connection class: R0 (autonomous)
- trust: 94/100
- quality: 63/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.bryantrudy24%2Fsaax-protocol
- tools: https://api.protogrid.dev/v1/servers/io.github.bryantrudy24%2Fsaax-protocol/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-100% +updated-15d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 63/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_commitment (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_routing_fee (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_commitment (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,865 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 16 tool changes in 30 days
- fail `stability.rug_pull`: 11 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 11, about 1,865 tokens to load them all
- tool set hash: 728f4faeb401f0e2e1b66ebf03312aea
- tools last changed: 2026-10-13T01:15:37.745Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.bryantrudy24/saax-protocol.svg)](https://protogrid.dev/servers/io.github.bryantrudy24/saax-protocol)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-13 `create_commitment` added
  - 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.
- 2026-10-10 `get_commitment_status` changed (description) **meaning changed**
  - before: Returns only the current lifecycle state for a given commitment ID. Call this for lightweight polling when the full commitment object is not needed. For the full commitment record, use get_commitment.
  - after: 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.
- 2026-10-10 `get_authority_validation` changed (description) **meaning changed**
  - before: PREMIUM. Validates an external authority proof (ap2-mandate, verifiable-intent, oauth-token, custom) against a commitment request: structure, signature, scope, and time validity. Requires an active SAAX Premium subscription.
  - after: Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.
- 2026-10-10 `get_evidence_verification` changed (description) **meaning changed**
  - before: PREMIUM. Validates externally-produced evidence against a commitment's acceptance criteria using the evidence abstraction (evaluateCriterion). Requires an active SAAX Premium subscription. Provide evidence, commitment, and criterion; returns satisfied | not_satisfied | insufficient_evidence with the evaluation reason.
  - after: Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.
- 2026-10-10 `get_commitment_status` changed (description) **meaning changed**
  - before: Takes { commitmentId } and returns ONLY the current lifecycle state for lightweight polling: { commitmentId, state }. Distinct from get_commitment (which returns the full manifest). Read-only and UNGATED — the commitment id is the access token. Returns not_found when the commitment does not exist, and invalid when the id fails format validation. state is one of: issued, authority_validated, accepted, executing, evidence_pending, evidence_submitted, verifying, fulfilled, failed, recovering, disputed, settled, finalized, cancelled, expired.
  - after: Returns only the current lifecycle state for a given commitment ID. Call this for lightweight polling when the full commitment object is not needed. For the full commitment record, use get_commitment.
- 2026-10-10 `list_commitments` changed (description) **meaning changed**
  - before: PREMIUM. Takes { subscriptionEmail }. Requires an active SAAX Premium subscription tied to that email (same gating as get_evidence_verification / get_authority_validation). Returns an array of commitment summaries (commitmentId, createdAt, state, capability, terms) recorded in this instance's commitment store — the SAME store get_commitment reads. Returns an empty array (not an error) when the subscriber has no commitments, and payment_required when the email has no active subscription. Read-only; never triggers settlement.
  - after: 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.
- 2026-10-10 `list_capabilities` changed (description) **meaning changed**
  - before: Returns the distinct capabilities among active suppliers with the supplier count per capability. Read-only; requires no payment. Used by agents to discover what SAAX currently routes.
  - after: 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.
- 2026-10-10 `get_commitment` changed (description) **meaning changed**
  - before: Takes a commitmentId. Validates the id format, looks up the Trade Manifest in the commitment store, and returns it. Returns a not-found response if the commitment does not exist. Read-only: never triggers settlement. Note: the MCP instance keeps its own in-process commitment store (issued commitments from this instance).
  - after: 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.
- 2026-10-10 `route_request` changed (description) **meaning changed**
  - before: Takes { capability, budget, deadline }. Sanitizes the input, ranks active suppliers against the capability using the gateway's ranking engine (scripts/rank-suppliers.js), and returns the ranked supplier list with scores, agent IDs, and payTo addresses. If no supplier clears the capability floor, returns a no_match response. This tool NEVER initiates payment — the buyer settles via the HTTP /route endpoint with the x402 challenge.
  - after: 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.
- 2026-10-10 `ping` changed (description) **meaning changed**
  - before: Liveness check. Returns ok.
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/io.github.bryantrudy24%2Fsaax-protocol/changes

## Remotes

- https://www.saax-protocol.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (11)

- `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_authority_validation`: Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.
- `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.
- `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.
- `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.
- `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.
- `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.
- `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.
- `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 lookup after routing, use get_commitment.