SAAX Protocol
MCP server by SAAX Protocol
Create and manage durable commitment records for agentic commerce, with evidence verification, disputes and recovery by replacement agents.
Connect to SAAX Protocol
No sign-in needed. Connect with SAAX Protocol’s own URL:
Paste it into any client that supports remote MCP servers. Your client talks to SAAX Protocol directly, not through mcp.tc.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/saax-protocolAbout
SAAX Protocol is a vendor-neutral commitment lifecycle layer for agentic commerce. Its tools discover routable capabilities and suppliers, prepare signed nonbinding proposals, accept them into commitments, submit and verify evidence, raise and resolve disputes, and let an independently authorized agent resume a commitment after the original worker stops.
The server runs as a hosted streamable HTTP endpoint at saax-protocol.com/mcp. Read-only discovery tools work without sign-in or an API key. Lifecycle actions require an EIP-712 authority proof, and a few tools require an active SAAX Premium subscription. The vendor labels live mainnet payments as public beta and escrow custody as testnet-only.
What you can do
- Discover routed capabilities and ranked suppliers
- Prepare free, signed, nonbinding proposals
- Accept proposals to create authenticated commitments
- Read commitment state, history and recovery status
- Submit, list and verify fulfillment evidence
- Raise, list and resolve disputes without financial transfer
- Resume, cancel or close commitments with an authority proof
Tools 26
get_protocol_infoReturn protocol version, capability count and specification URL.
get_routing_feeReturn the current routing fee schedule.
pingLightweight liveness check.
route_requestSubmit a capability request and get ranked supplier matches.
get_commitmentReturn the full commitment record by ID.
list_capabilitiesList indexed capabilities with supplier counts.
list_commitmentsList commitments for a subscription email (Premium).
get_commitment_statusReturn lifecycle state and recommended next action.
create_commitmentCreate a rail-neutral commitment between buyer and seller.
get_evidence_verificationVerify evidence against acceptance criteria (Premium).
get_authority_validationValidate an authority proof against a commitment (Premium).
get_commitment_historyReturn the append-only lifecycle journal for a commitment.
Show 14 more tools
get_recovery_statusReturn state, caller authorization and permitted recovery actions.
get_pending_actionsReturn lifecycle actions the caller may perform now.
resume_commitmentLet an authorized replacement agent continue a commitment.
cancel_commitmentCancel a commitment without any financial action.
close_commitmentClose a fulfilled commitment from settled to finalized.
prepare_commitmentPrepare a free, nonbinding signed proposal.
accept_commitmentAccept a signed proposal and create one authenticated commitment.
submit_evidenceSubmit fulfillment evidence for a commitment.
list_evidenceList evidence records for a commitment.
verify_evidenceMark a submitted evidence record verified or rejected.
raise_disputeRaise a dispute and move the commitment to disputed.
resolve_disputeRecord an evaluator decision on an open dispute.
list_disputesList dispute records for a commitment.
get_supplier_detailsReturn the detailed record for one indexed supplier.
Read from the live server on 15 Nov 2026.
Example prompts
List the capabilities currently routable through SAAX.
Check the status of commitment saax_abc123 and tell me the next action.
Prepare a signed proposal for a data-extraction capability.
Show the recovery status for this commitment so a replacement agent can continue.
Set up
Every client connects to saax-protocol.com. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http saax-protocol https://saax-protocol.com/mcp- Start Claude Code and type
/mcp. saax-protocol should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it SAAX Protocol and paste this URL:
https://saax-protocol.com/mcp- Click Add. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://saax-protocol.com/mcpand click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://saax-protocol.com/mcpas the server URL, then for authentication choose No authentication. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"saax-protocol": {
"url": "https://saax-protocol.com/mcp"
}
}
}VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"saax-protocol","type":"http","url":"https://saax-protocol.com/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"saax-protocol": {
"type": "http",
"url": "https://saax-protocol.com/mcp"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"saax-protocol": {
"serverUrl": "https://saax-protocol.com/mcp"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add saax-protocol --url https://saax-protocol.com/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.saax-protocol]
url = "https://saax-protocol.com/mcp"Gemini CLI
gemini mcp add --transport http saax-protocol https://saax-protocol.com/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"saax-protocol": {
"type": "http",
"url": "https://saax-protocol.com/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://saax-protocol.com/mcp.
Embed
Show SAAX Protocol in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/saax-protocol)<a href="https://mcp.tc/i/saax-protocol"><img src="https://mcp.tc/i/saax-protocol/badge.svg" alt="SAAX Protocol on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/saax-protocol.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/saax-protocol" title="SAAX Protocol on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/saax-protocol.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the SAAX Protocol card to your site.
Add the mcp.tc card for SAAX Protocol, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/saax-protocol.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="saax-protocol"><a href="https://mcp.tc/i/saax-protocol">SAAX Protocol on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/saax-protocol)
```
Reference: https://mcp.tc/embedChange history
We haven’t read this server’s tool list recently, so for now only edits by the server’s owner are recorded.
Nothing recorded yet. The History starts with our first read of this server.
FAQ
Can I paste mcp.tc/i/saax-protocol into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://saax-protocol.com/mcp, so your client talks to SAAX Protocol directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does SAAX Protocol need an API key or a sign-in?
No. SAAX Protocol doesn’t ask for an account or key.
Is SAAX Protocol a remote or a local server?
Remote. SAAX Protocol hosts it at https://saax-protocol.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can SAAX Protocol do?
It has 26 tools, including get_protocol_info, get_routing_fee and ping. You can discover routed capabilities and ranked suppliers, prepare free, signed, nonbinding proposals and accept proposals to create authenticated commitments.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to SAAX Protocol?
Partly. We haven’t read SAAX Protocol’s tool list lately, so for now its History tab shows only edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read SAAX Protocol’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with SAAX Protocol. This page was built from SAAX Protocol’s public metadata, last checked on 15 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.