SAAX Protocol
REMOTE · WWW.SAAX-PROTOCOL.COM
Governed commitment lifecycle and rail-agnostic settlement layer for agent-to-agent commerce.
Available components
Last scanned (6 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1054 tokens (~95/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://www.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=www.saax-protocol.com | CN=YR1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | RSA 2048 | SHA256-RSA | 5f0205c011cc027ff116e5552d3fb2d378e |
| SANs: www.saax-protocol.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 www.saax-protocol.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| saax-protocol.com. | absent | 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://www.saax-protocol.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.saax-protocol.com/mcp | HTTPS enforced | 308 | https://www.saax-protocol.com/mcp |
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 →
create_commitment Create a rail-neutral 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.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | yes | Objective acceptance criteria for fulfillment |
| buyerId | string | yes | The buyer's identity: 0x-address or agent id |
| evidenceRequirements | array | – | Evidence the seller must supply |
| recoveryPolicy | object | – | Recovery policy on failure |
| sellerId | string | yes | The seller's identity: 0x-address or agent id |
| settlementRail | string | – | The settlement rail as metadata. Never a prerequisite; 'unspecified' is valid. |
| terms | object | yes | The commercial terms: deliverable, price, deadline |
No output schema declared.
No examples provided.
get_authority_validation Validate an authority proof ~104
Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.
| Name | Type | Req | Description |
|---|---|---|---|
| commitment | – | yes | The commitment or requested action the proof must authorize |
| proof | – | yes | The AuthorityProof object (proofType, issuer, subject, scope, validFrom, validUntil, signature, verificationScheme, verificationMaterial) |
| subscriptionEmail | string | yes | The subscription email (must have an active SAAX Premium subscription) |
No output schema declared.
No examples provided.
get_commitment Get a commitment manifest ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| commitmentId | string | yes | The commitment id (0x-prefixed or agent-id style) to look up |
No output schema declared.
No examples provided.
get_commitment_status Get a commitment's lifecycle state ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| commitmentId | string | yes | The commitment id to poll for its lifecycle state |
No output schema declared.
No examples provided.
get_evidence_verification Verify evidence against acceptance criteria ~121
Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.
| Name | Type | Req | Description |
|---|---|---|---|
| commitment | – | yes | The commitment object the evidence binds to |
| criterion | – | yes | The verification policy / acceptance criterion |
| evidence | – | yes | The evidence object (evidenceId, evidenceType, issuer, subject, payload, payloadHash, signature, verificationScheme, commitmentId, acceptanceCriterionId, ...) |
| subscriptionEmail | string | yes | The subscription email (must have an active SAAX Premium subscription) |
No output schema declared.
No examples provided.
get_protocol_info Get SAAX Protocol information ~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_routing_fee Get SAAX 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.
list_capabilities List routed 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 List commitments for a subscriber ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| subscriptionEmail | string | yes | The subscription email (must have an active SAAX Premium subscription) |
No output schema declared.
No examples provided.
ping 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.
route_request Route a demand to ranked suppliers ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Maximum budget in USDC the buyer will pay |
| capability | string | yes | The capability demanded, e.g. 'security scan' |
| deadline | number | – | Deadline in seconds from now for delivery |
No output schema declared.
No examples provided.
How do I install the SAAX Protocol MCP server?
SAAX Protocol is a hosted endpoint at https://www.saax-protocol.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.saax-protocol.com
claude mcp add --transport http bryantrudy24-saax-protocol 'https://www.saax-protocol.com/mcp'
What is the SAAX Protocol MCP server?
SAAX Protocol is an MCP server listed in the public MCP registry as io.github.bryantrudy24/saax-protocol. Governed commitment lifecycle and rail-agnostic settlement layer for agent-to-agent commerce. This page covers its hosted endpoint (https://www.saax-protocol.com/mcp).
Is the SAAX Protocol MCP server safe to use?
SAAX Protocol scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SAAX Protocol MCP server expose?
SAAX Protocol exposes 11 tools: get_protocol_info, get_routing_fee, ping, route_request, get_commitment, and 6 more. Their descriptions and schemas cost roughly 1,054 tokens of context every time the server is loaded.
Does the SAAX Protocol MCP server require authentication?
No. We connected to SAAX Protocol without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SAAX Protocol MCP server still maintained?
SAAX Protocol is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.