SAAX Protocol
by saax-protocol.com in Other
Governed commitment lifecycle and rail-agnostic settlement layer for agent-to-agent commerce.
https://www.saax-protocol.com/mcp- Tools
- 11
- open to any client
- Uptime
- 95.5%
- last 30 days
- Response time
- 532 ms
- 1.4 s slowest 5%
- Last check
- Passed
- 7 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"saax-protocol": {
"type": "http",
"url": "https://www.saax-protocol.com/mcp"
}
}
}11 tools
- get_protocol_info
Returns the SAAX Protocol version, available capability count, and the URL to the specification. Call this when an agent needs a one-time overview of the protocol. For pricing, use get_routing_fee. For the full capability list, use list_capabilities. For a liveness check, use…
- get_routing_fee
Returns the current routing fee schedule. Call this before initiating a routing request to determine the expected cost. For capability discovery, use list_capabilities. For protocol overview, use get_protocol_info.
- ping
Returns a lightweight liveness response. Call this to verify the endpoint is reachable. Do not use for discovery, capability listing, or pricing — use get_protocol_info, list_capabilities, or get_routing_fee instead.
- route_request
Submits a capability request and returns ranked supplier matches. Commitment creation with payment runs through the HTTP POST /route endpoint, not this tool. Use list_capabilities first to discover available capabilities. For commitment lookup after routing, use get_commitment.
- get_commitment
Returns the full commitment object for a given commitment ID — including terms, state, manifest hash, and evidence references. Call this when an agent needs the complete commitment record. For status-only polling, use get_commitment_status. For listing all commitments for a…
- list_capabilities
Returns the capabilities currently indexed by the SAAX Router, with supplier counts per capability. Call this to discover what can be routed. For pricing of a specific capability, use get_routing_fee. For protocol overview, use get_protocol_info.
- list_commitments
Returns all commitments associated with a subscription email. Requires an active SAAX Premium subscription. Call this to retrieve commitment history for a subscriber. For a single commitment by ID, use get_commitment. For status-only checks, use get_commitment_status.
- get_commitment_status
Returns only the current lifecycle state for a given commitment ID, plus the recommended next action for the calling agent. Call this before retrying any commitment that timed out — an unknown outcome is a status check, not another POST. The next_action field tells the agent…
- create_commitment
Creates a governed commitment between a buyer and a seller and persists it to the SAAX commitment store. The commitment is settlement-rail-neutral: settlementRail is metadata only (x402, mpp, ap2, acp, or unspecified) and is NEVER a prerequisite. Returns the new commitment id…
- get_evidence_verification
Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.
- get_authority_validation
Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 7 h ago | Passed | 200 | 312 ms |
| 17 h ago | Passed | 200 | 1.3 s |
| 26 h ago | Passed | 200 | 954 ms |
| 35 h ago | Passed | 200 | 866 ms |
| 43 h ago | initialize returned HTTP 500 | 500 | 275 ms |
Show 10 older checks
| 2 days ago | Passed | 200 | 1.3 s |
| 3 days ago | Passed | 200 | 411 ms |
| 3 days ago | Passed | 200 | 1.1 s |
| 4 days ago | Passed | 200 | 1.5 s |
| 4 days ago | Passed | 200 | 1.0 s |
| 4 days ago | Passed | 200 | 502 ms |
| 5 days ago | Passed | 200 | 1.4 s |
| 5 days ago | Passed | 200 | 348 ms |
| 6 days ago | Passed | 200 | 988 ms |
| 6 days ago | Passed | 200 | 291 ms |