Skip to content

SAAX Protocol MCP server

io.github.bryantrudy24/saax-protocolbryantrudy24streamable-httpv1.0.4Scanned

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

26 tools: 1 can delete or cancel things, 1 do something that can't be undone, 8 change things and 16 only read.

Tools: 1 delete, 1 irreversible, 8 write, 16 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SAAX Protocol MCP server can do

The SAAX Protocol MCP server is published by the GitHub account bryantrudy24. It has 26 tools. It can delete or cancel things (1 tool: cancel_commitment), do things that cannot be undone, such as sending, paying or publishing (create_commitment) and create or change data (8 tools: route_request, resume_commitment, close_commitment, prepare_commitment and 4 more). 16 tools only read.

1 tool reads private data (list_commitments); 2 tools bring in text other people can write (get_protocol_info and list_commitments).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

26 tools

Deletes or cancels 1Claude Code: deny
  • cancel_commitmentCancels a commitment when the caller (verified by EIP-712 proof) holds buyer or authority authorization with cancel scope.No findings

    Why it is in this group

    • The name "cancel_commitment" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    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.
Can't be undone 1Claude Code: ask
  • create_commitmentCreates a governed commitment between a buyer and a seller and persists it to the SAAX commitment store.No findings

    Why it is in this group

    • The name "create_commitment" says "create": a word for a change.
    • The input carries an amount (input.terms.price.amount) and a currency, so it moves money.
    Description, as the server wrote it
    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.
Changes things 8Claude Code: ask
  • accept_commitmentAccepts a signed preflight proposal with explicit buyer authorization and creates exactly ONE authenticated SAAX commitment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • close_commitmentCloses a fulfilled commitment (settled -> finalized) when the caller (verified by EIP-712 proof) holds system or authority authorization.No findings

    Why it is in this group

    • The name "close_commitment" says "close": a word for a change.
    Description, as the server wrote it
    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.
  • prepare_commitmentPrepares a free, NONBINDING signed proposal (preflight) for a desired SAAX capability.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • raise_disputeRaises a durable dispute on a commitment and transitions it to the disputed state.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • resume_commitmentLets an independently authorized replacement agent continue a commitment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • route_requestSubmits a capability request and returns ranked supplier matches.No findings

    Why it is in this group

    • The name "route_request" says "request": a word for a change.
    Description, as the server wrote it
    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.
  • submit_evidenceDurably submits evidence for a commitment.No findings

    Why it is in this group

    • The name "submit_evidence" says "submit": a word for a change.
    Description, as the server wrote it
    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.
  • verify_evidenceSets the verification status of a submitted evidence record to verified or rejected.No findings

    Why it is in this group

    • The description's first verb is "set": a word for a change.
    Description, as the server wrote it
    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.
Only reads 16Show 16 read-only tools
  • get_authority_validationValidates an authority proof against a commitment.No findings

    Why it is in this group

    • The name "get_authority_validation" says "get": a word for reading.
    Description, as the server wrote it
    Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.
  • get_commitmentReturns the full commitment object for a given commitment ID — including terms, state, manifest hash, and evidence references.No findings

    Why it is in this group

    • The name "get_commitment" says "get": a word for reading.
    Description, as the server wrote it
    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_historyReturns the append-only lifecycle event ledger for a commitment � every recorded transition with actor, authority reference, state version, and evidence reference.No findings

    Why it is in this group

    • The name "get_commitment_history" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_commitment_statusReturns only the current lifecycle state for a given commitment ID, plus the recommended next action for the calling agent.No findings

    Why it is in this group

    • The name "get_commitment_status" says "get": a word for reading.
    Description, as the server wrote it
    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_verificationVerifies external evidence against a commitment's acceptance criteria.No findings

    Why it is in this group

    • The name "get_evidence_verification" says "get": a word for reading.
    Description, as the server wrote it
    Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.
  • get_pending_actionsReturns 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 c…No findings

    Why it is in this group

    • The name "get_pending_actions" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_protocol_infoReturns the SAAX Protocol version, available capability count, and the URL to the specification.Reads text others writeNo findings

    Why it is in this group

    • The name "get_protocol_info" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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_recovery_statusReturns the authoritative commitment state, the caller's authorization status (active/revoked/expired), whether the commitment is recoverable, and the caller's permitted next actio…No findings

    Why it is in this group

    • The name "get_recovery_status" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_routing_feeReturns the current routing fee schedule.No findings

    Why it is in this group

    • The name "get_routing_fee" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_supplier_detailsReturns the detailed record for one supplier in the SAAX Router index: identifier, name, description, services (name/endpoint/version), owner and source provenance.No findings

    Why it is in this group

    • The name "get_supplier_details" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_capabilitiesReturns the capabilities currently indexed by the SAAX Router, with supplier counts per capability.No findings

    Why it is in this group

    • The name "list_capabilities" says "list": a word for reading.
    Description, as the server wrote it
    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_commitmentsReturns all commitments associated with a subscription email.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_commitments" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "return" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.
  • list_disputesReturns the durable dispute records for a commitment (dispute identifiers, status, resolution, attribution, timestamps).No findings

    Why it is in this group

    • The name "list_disputes" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • list_evidenceReturns the durable evidence records for a commitment (stable identifiers, integrity references, submitter attribution, status, timestamps � never raw payload content).No findings

    Why it is in this group

    • The name "list_evidence" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • pingReturns a lightweight liveness response.No findings

    Why it is in this group

    • The name "ping" says "ping": a word for reading.
    Description, as the server wrote it
    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.
  • resolve_disputeRecords an evaluator decision on an open dispute and transitions the commitment to the canonical nonfinancial outcome (continue|rework|satisfied|against).No findings

    Why it is in this group

    • The name "resolve_dispute" says "resolve": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:03 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (1 destructive, 1 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://saax-protocol.com/mcp: tools/list returned 26 tools to an anonymous client, including cancel_commitment (destructive), create_commitment (irreversible), route_request (write), resume_commitment (write), close_commitment (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 4 to 10
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 2 to 4

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 10.View diff
    • Tools that change things, listed without credentials: 4 to 10
  2. Tools15 added.+15 addedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 4.View diff
    • Tools that change things, listed without credentials: 2 to 4

Install

Pinned to version 1.0.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__saax-protocol__get_protocol_info",
      "mcp__saax-protocol__get_routing_fee",
      "mcp__saax-protocol__ping",
      "mcp__saax-protocol__get_commitment",
      "mcp__saax-protocol__list_capabilities",
      "mcp__saax-protocol__list_commitments",
      "mcp__saax-protocol__get_commitment_status",
      "mcp__saax-protocol__get_evidence_verification",
      "mcp__saax-protocol__get_authority_validation",
      "mcp__saax-protocol__get_commitment_history",
      "mcp__saax-protocol__get_recovery_status",
      "mcp__saax-protocol__get_pending_actions",
      "mcp__saax-protocol__list_evidence",
      "mcp__saax-protocol__resolve_dispute",
      "mcp__saax-protocol__list_disputes",
      "mcp__saax-protocol__get_supplier_details"
    ],
    "ask": [
      "mcp__saax-protocol__route_request",
      "mcp__saax-protocol__create_commitment",
      "mcp__saax-protocol__resume_commitment",
      "mcp__saax-protocol__close_commitment",
      "mcp__saax-protocol__prepare_commitment",
      "mcp__saax-protocol__accept_commitment",
      "mcp__saax-protocol__submit_evidence",
      "mcp__saax-protocol__verify_evidence",
      "mcp__saax-protocol__raise_dispute"
    ],
    "deny": [
      "mcp__saax-protocol__cancel_commitment"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as saax-protocol. Review it before you use it.

Capability tags behind 2 rules
  • mcp__saax-protocol__get_protocol_info untrusted-input
  • mcp__saax-protocol__list_commitments private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.bryantrudy24/saax-protocol/verify?hash=bcd8f580bc93b9bfebb375dfd4a41790014e8ca93b89f19cecfb0466d4e67821" | jq -e '.changed == false'

Pinned hash bcd8f580bc93, from Nov 14, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.bryantrudy24/saax-protocol/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.bryantrudy24/saax-protocol
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.bryantrudy24/saax-protocol.svg)](https://radar.anlyon.com/servers/io.github.bryantrudy24/saax-protocol)

Source: MCP Registry · repository. Synced Nov 14, 2026, 13:17 UTC.

SAAX Protocol MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SAAX Protocol MCP server safe?

No scan can promise that. What its definitions show: 26 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SAAX Protocol MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_commitment.

Can the SAAX Protocol MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: create_commitment.

What tools does the SAAX Protocol MCP server have?

26 tools: 1 destructive, 1 irreversible, 8 write, 16 read. cancel_commitment, create_commitment, route_request, resume_commitment, close_commitment, prepare_commitment, accept_commitment, submit_evidence and 18 more.

Does the SAAX Protocol MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SAAX Protocol MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SAAX Protocol MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.