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

Durable commitment lifecycle, verification, governance and recovery layer for agentic commerce.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

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

## 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-21.

- **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 26 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3799 tokens (~146/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 26 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 26 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://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://saax-protocol.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "bryantrudy24-saax-protocol": {
      "type": "http",
      "url": "https://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-20 (score 69, +1)

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

### 2026-11-18 (score 68, +1)

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

### 2026-11-16 (score 67, +1)

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

### 2026-11-15 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 66)

First indexed and scored.

## MCP tools (26)

### `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)

### `get_commitment_history` (~147 tokens)

Get the durable lifecycle journal for a commitment

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 the commitment. Read-only; reconciles the authoritative commitment before returning. For a compact status, use get_commitment_status; for recovery guidance, use get_recovery_status.

Input parameters:

- `agentId` (string, required): The caller's durable agent identifier
- `commitmentId` (string, required): The commitment id
- `proof` (object, required): EIP-712 AuthorityProof signed by the caller (issuer = signer)
- `role` (string, required): The caller's role on this commitment

### `get_recovery_status` (~156 tokens)

Get recovery status and pending actions for a commitment

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 authorization record before returning. The caller must present an EIP-712 authority proof. Read-only. For the raw journal, use get_commitment_history; to continue a workflow, use resume_commitment.

Input parameters:

- `agentId` (string, required): The caller's durable agent identifier
- `commitmentId` (string, required): The commitment id
- `proof` (object, required): EIP-712 AuthorityProof signed by the caller (issuer = signer)
- `role` (string, required): The caller's role on this commitment

### `get_pending_actions` (~125 tokens)

Get the caller's permitted next lifecycle 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 recovery context, use get_recovery_status.

Input parameters:

- `agentId` (string, required): The caller's durable agent identifier
- `commitmentId` (string, required): The commitment id
- `proof` (object, required): EIP-712 AuthorityProof signed by the caller (issuer = signer)
- `role` (string, required): The caller's role on this commitment

### `resume_commitment` (~280 tokens)

Resume a commitment after the original agent terminated

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 transition engine. The replacement agent must hold its OWN durable authorization (no automatic inheritance). Duplicate requests are idempotent. Financial transitions (settle/finalize with settlement, escrow release, refunds) are NOT exposed. For inspection first, use get_recovery_status or get_pending_actions.

Input parameters:

- `action` (string, required): The lifecycle action to execute: cancel, accept, authorize, execute, complete, submit, verify, fulfill, recover, dispute (nonfinancial subset)
- `agentId` (string, required): The caller's durable agent identifier
- `authorityRef` (string): Optional external authority reference to record on the event
- `commitmentId` (string, required): The commitment id
- `evidenceRef` (string): Optional evidence reference to bind to the transition
- `expectedVersion` (integer): Optimistic-concurrency guard: the state version the caller observed
- `idempotencyRef` (string): Caller-scoped idempotency reference (>= 8 chars) for safe retries
- `proof` (object, required): EIP-712 AuthorityProof signed by the caller (issuer = signer)
- `role` (string, required): The caller's role on this commitment

### `cancel_commitment` (~160 tokens)

Cancel a 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. Idempotent via idempotencyRef.

Input parameters:

- `agentId` (string, required): The caller's durable agent identifier
- `commitmentId` (string, required): The commitment id
- `idempotencyRef` (string): Caller-scoped idempotency reference
- `proof` (object, required): EIP-712 AuthorityProof signed by the caller (issuer = signer)
- `reason` (string): Cancellation reason (recorded as authority reference)
- `role` (string, required): The caller's role (cancel requires buyer or authority)

### `close_commitment` (~148 tokens)

Close a fulfilled 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 first. Idempotent via idempotencyRef.

Input parameters:

- `agentId` (string, required): The caller's durable agent identifier
- `commitmentId` (string, required): The commitment id
- `idempotencyRef` (string): Caller-scoped idempotency reference
- `proof` (object, required): EIP-712 AuthorityProof signed by the caller (issuer = signer)
- `role` (string, required): The caller's role (close requires system or authority)

### `prepare_commitment` (~224 tokens)

Prepare a free, nonbinding signed proposal (preflight)

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 binding the request digest and normalized terms. Creates NO agreement, payment, custody deposit, service execution, resource reservation, or spending authority. A provider signature is NOT buyer acceptance. No preflight fee. Errors are typed DSC_* codes.

Input parameters:

- `capability` (object, required): Desired capability
- `clientNonce` (string, required): Caller-chosen nonce (echoed; replay idempotency)
- `constraints` (object): Optional constraints
- `financialProfile` (object, required): Financial axes
- `intendedParties` (object): Intended parties
- `issuedAt` (string, required): ISO-8601 client timestamp
- `profileVersion` (string, required): SAAX Discovery profile version (e.g. 1.0.0)
- `schema` (object, required): Expected commitment schema
- `units` (object, required): Amount + unit

### `accept_commitment` (~245 tokens)

Accept a signed proposal and create exactly one authenticated 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 the BUYER'S SIGNATURE over the exact proposal digest and terms digest, durably accepts once (single-writer store), and returns the operation + commitment. Creates NO payment authorization, custody funding, service execution, or release. A buyer acceptance is NOT a payment authorization or evaluator release verdict. Errors are typed DSC_* codes. Idempotent: same idempotencyKey + same request returns the same operation; same key + different request -> DSC_NONCE_CONFLICT; a single-use proposal cannot be re-accepted under a new key -> DSC_PROPOSAL_REUSED.

Input parameters:

- `acceptance` (object, required): The buyer acceptance contract (schemaVersion acceptance-v1, action accept_commitment, domain saax:acceptance:v1, signed by the buyer)
- `idempotencyKey` (string, required): Caller-scoped idempotency key (>= 8 chars)
- `proposal` (object, required): The signed proposal returned by prepare_commitment (full object incl. signature)

### `submit_evidence` (~283 tokens)

Submit fulfillment 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 durable registry). The evidence envelope is validated for structure and size, bound to the commitment and optional acceptance criterion, and persisted with the verified submitter attribution and an integrity payload hash. Idempotent per idempotencyRef: a replay returns the original record; reuse with a materially different payload is rejected. Submission does NOT transition the commitment state and does NOT trigger settlement, escrow release, or finalization � those require separate authorized lifecycle actions.

Input parameters:

- `agentId` (string, required): The caller's agent identity (bound to the verified principal)
- `commitmentId` (string, required): The commitment ID the evidence binds to
- `criterionId` (string): The acceptance criterion ID this evidence addresses, if applicable
- `evidence` (required): The evidence envelope: evidenceType, issuer, subject, payload, payloadHash, signature, verificationScheme, commitmentId, acceptanceCriterionId, provenance
- `idempotencyRef` (string): Stable idempotency reference; replay-safe
- `proof` (required): The EIP-712 AuthorityProof: authorityProofId, issuer, subject, validFrom, validUntil, scope, signature, verificationScheme=eip712

### `list_evidence` (~161 tokens)

List evidence for a commitment

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 authorization on the commitment. Commitment-scoped: callers with no authorization on the commitment see nothing. Optional status filter (submitted|verified|rejected|disputed). Read-only.

Input parameters:

- `agentId` (string, required): The caller's agent identity
- `commitmentId` (string, required): The commitment ID whose evidence to list
- `limit` (number): Max records (default 50)
- `offset` (number): Pagination offset
- `proof` (required): The EIP-712 AuthorityProof
- `status` (string): Filter by evidence status

### `verify_evidence` (~192 tokens)

Verify or reject submitted 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). Idempotent per verdict: re-verifying with the same verdict replays the original outcome; changing a verified record to rejected (or vice versa) is rejected without a dispute path. Does NOT auto-transition the commitment state � the caller must perform the authorized lifecycle transition separately. Rejection requires a reason.

Input parameters:

- `agentId` (string, required): The caller's agent identity
- `evidenceId` (string, required): The evidence record ID to verify
- `expectedVersion` (number): Optimistic-concurrency expected version
- `proof` (required): The EIP-712 AuthorityProof
- `reason` (string): Required when verdict=rejected
- `verdict` (string, required): The evaluator verdict

### `raise_dispute` (~198 tokens)

Raise a dispute on a commitment

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 only be raised from evidence_submitted or fulfilled states per the canonical lifecycle. Dispute resolution NEVER triggers a financial transfer. Idempotent per idempotencyRef.

Input parameters:

- `agentId` (string, required): The caller's agent identity (bound to the verified principal)
- `commitmentId` (string, required): The commitment ID being disputed
- `disputeId` (string): Stable dispute identifier; generated if omitted
- `evidenceRefs` (array): Reference identifiers of supporting evidence records
- `idempotencyRef` (string): Stable idempotency reference; replay-safe
- `proof` (required): The EIP-712 AuthorityProof
- `reason` (string, required): Dispute reason (at least 8 characters)

### `resolve_dispute` (~171 tokens)

Resolve an open 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 EVALUATOR authorization on the commitment (verified in-transaction). Resolution NEVER executes a financial transfer or settlement. Idempotent per idempotencyRef.

Input parameters:

- `agentId` (string, required): The caller's agent identity (bound to the verified principal)
- `disputeId` (string, required): The dispute ID to resolve
- `idempotencyRef` (string): Stable idempotency reference; replay-safe
- `outcome` (string, required): Nonfinancial resolution outcome
- `proof` (required): The EIP-712 AuthorityProof
- `reason` (string): Resolution rationale

### `list_disputes` (~142 tokens)

List disputes for a commitment

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-scoped: callers with no authorization see nothing. Optional status filter. Read-only.

Input parameters:

- `agentId` (string, required): The caller's agent identity
- `commitmentId` (string, required): The commitment ID whose disputes to list
- `limit` (number): Max records (default 50)
- `offset` (number): Pagination offset
- `proof` (required): The EIP-712 AuthorityProof
- `status` (string): Filter by dispute status

### `get_supplier_details` (~113 tokens)

Get 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 supplier before preparing a commitment. Read-only; exact supplier_id match only (no enumeration). A registry entry is not a guarantee of service quality or verification.

Input parameters:

- `supplier_id` (string, required): The supplier identifier (agent_id from list_capabilities/route_request results, or its decimal string form)

## Diagnostics

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

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 66

## 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. Durable commitment lifecycle, verification, governance and recovery layer for agentic commerce. This page covers its hosted endpoint (https://saax-protocol.com/mcp).

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

SAAX Protocol scores 69 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 26 tools: get_protocol_info, get_routing_fee, ping, route_request, get_commitment, and 21 more. Their descriptions and schemas cost roughly 3,799 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 21 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://saax-protocol.com/mcp
- Repository: https://github.com/bryantrudy24/saax-protocol
- Website: https://saax-protocol.com/
- Changelog RSS feed: https://verifymcp.io/servers/bryantrudy24-saax-protocol/saax-protocol.xml
- Changelog JSON feed: https://verifymcp.io/servers/bryantrudy24-saax-protocol/saax-protocol/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/bryantrudy24-saax-protocol/saax-protocol.json
- HTML version of this page: https://verifymcp.io/servers/bryantrudy24-saax-protocol/saax-protocol
