saax-protocol

Tools

6 tools: 0 read-only, 6 change data, 0 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 732 tokens of tool definitions and a 162 ms handshake.

• changes dataget_protocol_infoReturns the protocol's name, version, description, supported settlement rails, commitment lifecycle, and routing fee schedule.
• changes dataget_routing_feeReturns the per-request routing fee in microUSDC and USD, and the settlement asset / chain the fee is settled in.
• changes datapingLiveness check. Returns ok.
• changes dataroute_requestTakes { capability, budget, deadline }. Sanitizes the input, ranks active suppliers against the capability using the gateway's ranking engine (scripts/rank-suppliers.js), and returns the ranked supplier list with scores, agent IDs, and payTo addresses. If no supplier clears the capability floor, ...
• changes dataget_commitmentTakes a commitmentId. Validates the id format, looks up the Trade Manifest in the commitment store, and returns it. Returns a not-found response if the commitment does not exist. Read-only: never triggers settlement. Note: the MCP instance keeps its own in-process commitment store (issued commitm...
• changes datalist_capabilitiesReturns the distinct capabilities among active suppliers with the supplier count per capability. Read-only; requires no payment. Used by agents to discover what SAAX currently routes.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-06, 162 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-072026-10-06

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Bookings and appointments, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/ax-router.vercel.app/mcp.svg)](https://7it.co.il/7maps/s/ax-router.vercel.app/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=ax-router.vercel.app%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/ax-router.vercel.app/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/ax-router.vercel.app/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=ax-router.vercel.app%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.