Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SAAX Protocol

REMOTE · SAAX-PROTOCOL.COM

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

+3 this week 69 Trust /100

Last scanned (18 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://saax-protocol.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=saax-protocol.com CN=YR2,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 RSA 2048 SHA256-RSA 6f4e84ec65ffc1a2cdb31ac484ad2dd4f96
SANs: saax-protocol.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of saax-protocol.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
saax-protocol.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://saax-protocol.com/mcp Verified 200
http (plaintext) http://saax-protocol.com/mcp HTTPS enforced 308 https://saax-protocol.com/mcp
MCP tools · 26 exposed · ~3,799 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
accept_commitment ~245

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.

NameTypeReqDescription
acceptanceobjectyesThe buyer acceptance contract (schemaVersion acceptance-v1, action accept_commitment, domain saax:acceptance:v1, signed by the buyer)
idempotencyKeystringyesCaller-scoped idempotency key (>= 8 chars)
proposalobjectyesThe signed proposal returned by prepare_commitment (full object incl. signature)

No output schema declared.

No examples provided.

cancel_commitment ~160

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.

NameTypeReqDescription
agentIdstringyesThe caller's durable agent identifier
commitmentIdstringyesThe commitment id
idempotencyRefstring–Caller-scoped idempotency reference
proofobjectyesEIP-712 AuthorityProof signed by the caller (issuer = signer)
reasonstring–Cancellation reason (recorded as authority reference)
rolestringyesThe caller's role (cancel requires buyer or authority)

No output schema declared.

No examples provided.

close_commitment ~148

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.

NameTypeReqDescription
agentIdstringyesThe caller's durable agent identifier
commitmentIdstringyesThe commitment id
idempotencyRefstring–Caller-scoped idempotency reference
proofobjectyesEIP-712 AuthorityProof signed by the caller (issuer = signer)
rolestringyesThe caller's role (close requires system or authority)

No output schema declared.

No examples provided.

create_commitment ~230

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.

NameTypeReqDescription
acceptanceCriteriaarrayyesObjective acceptance criteria for fulfillment
buyerIdstringyesThe buyer's identity: 0x-address or agent id
evidenceRequirementsarray–Evidence the seller must supply
recoveryPolicyobject–Recovery policy on failure
sellerIdstringyesThe seller's identity: 0x-address or agent id
settlementRailstring–The settlement rail as metadata. Never a prerequisite; 'unspecified' is valid.
termsobjectyesThe commercial terms: deliverable, price, deadline

No output schema declared.

No examples provided.

get_authority_validation ~104

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

NameTypeReqDescription
commitment–yesThe commitment or requested action the proof must authorize
proof–yesThe AuthorityProof object (proofType, issuer, subject, scope, validFrom, validUntil, signature, verificationScheme, verificationMaterial)
subscriptionEmailstringyesThe subscription email (must have an active SAAX Premium subscription)

No output schema declared.

No examples provided.

get_commitment ~91

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.

NameTypeReqDescription
commitmentIdstringyesThe commitment id (0x-prefixed or agent-id style) to look up

No output schema declared.

No examples provided.

get_commitment_history ~147

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.

NameTypeReqDescription
agentIdstringyesThe caller's durable agent identifier
commitmentIdstringyesThe commitment id
proofobjectyesEIP-712 AuthorityProof signed by the caller (issuer = signer)
rolestringyesThe caller's role on this commitment

No output schema declared.

No examples provided.

get_commitment_status ~99

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.

NameTypeReqDescription
commitmentIdstringyesThe commitment id to poll for its lifecycle state

No output schema declared.

No examples provided.

get_evidence_verification ~121

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

NameTypeReqDescription
commitment–yesThe commitment object the evidence binds to
criterion–yesThe verification policy / acceptance criterion
evidence–yesThe evidence object (evidenceId, evidenceType, issuer, subject, payload, payloadHash, signature, verificationScheme, commitmentId, acceptanceCriterionId, ...)
subscriptionEmailstringyesThe subscription email (must have an active SAAX Premium subscription)

No output schema declared.

No examples provided.

get_pending_actions ~125

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.

NameTypeReqDescription
agentIdstringyesThe caller's durable agent identifier
commitmentIdstringyesThe commitment id
proofobjectyesEIP-712 AuthorityProof signed by the caller (issuer = signer)
rolestringyesThe caller's role on this commitment

No output schema declared.

No examples provided.

get_protocol_info ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_recovery_status ~156

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.

NameTypeReqDescription
agentIdstringyesThe caller's durable agent identifier
commitmentIdstringyesThe commitment id
proofobjectyesEIP-712 AuthorityProof signed by the caller (issuer = signer)
rolestringyesThe caller's role on this commitment

No output schema declared.

No examples provided.

get_routing_fee ~48

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_supplier_details ~113

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.

NameTypeReqDescription
supplier_idstringyesThe supplier identifier (agent_id from list_capabilities/route_request results, or its decimal string form)

No output schema declared.

No examples provided.

list_capabilities ~57

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_commitments ~79

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.

NameTypeReqDescription
subscriptionEmailstringyesThe subscription email (must have an active SAAX Premium subscription)

No output schema declared.

No examples provided.

list_disputes ~142

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.

NameTypeReqDescription
agentIdstringyesThe caller's agent identity
commitmentIdstringyesThe commitment ID whose disputes to list
limitnumber–Max records (default 50)
offsetnumber–Pagination offset
proof–yesThe EIP-712 AuthorityProof
statusstring–Filter by dispute status

No output schema declared.

No examples provided.

list_evidence ~161

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.

NameTypeReqDescription
agentIdstringyesThe caller's agent identity
commitmentIdstringyesThe commitment ID whose evidence to list
limitnumber–Max records (default 50)
offsetnumber–Pagination offset
proof–yesThe EIP-712 AuthorityProof
statusstring–Filter by evidence status

No output schema declared.

No examples provided.

ping ~51

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_commitment ~224

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.

NameTypeReqDescription
capabilityobjectyesDesired capability
clientNoncestringyesCaller-chosen nonce (echoed; replay idempotency)
constraintsobject–Optional constraints
financialProfileobjectyesFinancial axes
intendedPartiesobject–Intended parties
issuedAtstringyesISO-8601 client timestamp
profileVersionstringyesSAAX Discovery profile version (e.g. 1.0.0)
schemaobjectyesExpected commitment schema
unitsobjectyesAmount + unit

No output schema declared.

No examples provided.

raise_dispute ~198

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.

NameTypeReqDescription
agentIdstringyesThe caller's agent identity (bound to the verified principal)
commitmentIdstringyesThe commitment ID being disputed
disputeIdstring–Stable dispute identifier; generated if omitted
evidenceRefsarray–Reference identifiers of supporting evidence records
idempotencyRefstring–Stable idempotency reference; replay-safe
proof–yesThe EIP-712 AuthorityProof
reasonstringyesDispute reason (at least 8 characters)

No output schema declared.

No examples provided.

resolve_dispute ~171

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.

NameTypeReqDescription
agentIdstringyesThe caller's agent identity (bound to the verified principal)
disputeIdstringyesThe dispute ID to resolve
idempotencyRefstring–Stable idempotency reference; replay-safe
outcomestringyesNonfinancial resolution outcome
proof–yesThe EIP-712 AuthorityProof
reasonstring–Resolution rationale

No output schema declared.

No examples provided.

resume_commitment ~280

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.

NameTypeReqDescription
actionstringyesThe lifecycle action to execute: cancel, accept, authorize, execute, complete, submit, verify, fulfill, recover, dispute (nonfinancial subset)
agentIdstringyesThe caller's durable agent identifier
authorityRefstring–Optional external authority reference to record on the event
commitmentIdstringyesThe commitment id
evidenceRefstring–Optional evidence reference to bind to the transition
expectedVersioninteger–Optimistic-concurrency guard: the state version the caller observed
idempotencyRefstring–Caller-scoped idempotency reference (>= 8 chars) for safe retries
proofobjectyesEIP-712 AuthorityProof signed by the caller (issuer = signer)
rolestringyesThe caller's role on this commitment

No output schema declared.

No examples provided.

route_request ~104

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.

NameTypeReqDescription
budgetnumber–Maximum budget in USDC the buyer will pay
capabilitystringyesThe capability demanded, e.g. 'security scan'
deadlinenumber–Deadline in seconds from now for delivery

No output schema declared.

No examples provided.

submit_evidence ~283

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.

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

No output schema declared.

No examples provided.

verify_evidence ~192

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.

NameTypeReqDescription
agentIdstringyesThe caller's agent identity
evidenceIdstringyesThe evidence record ID to verify
expectedVersionnumber–Optimistic-concurrency expected version
proof–yesThe EIP-712 AuthorityProof
reasonstring–Required when verdict=rejected
verdictstringyesThe evaluator verdict

No output schema declared.

No examples provided.

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.

remote · saax-protocol.com

# add to Claude Code
claude mcp add --transport http bryantrudy24-saax-protocol 'https://saax-protocol.com/mcp'
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.