SafeRoute
REMOTE · API.USESAFEROUTE.COM
Noncustodial Base x402 payment control and seller settlement recovery
Available components
Last scanned (8 hours ago)
Scores higher than 55% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Crypto and Web3
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Oct 26 0
- “check_base_swap” added an optional parameter “discoverySource” cosmetic
- “get_safe_swap_quote” added an optional parameter “discoverySource” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- Server version: 0.17.0 → 0.18.1 functional
- 26 Aug 26 0
- First check of Injection markers: pass security
- First check of Judged manipulation: pass security
- Tool “guard_base_trade” rewrote its description, which is the text the model reads security
- First check of Destructive annotations: 0 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 0.16.0 → 0.17.0 functional
- 22 Aug 26 0
- Server version: 0.15.0 → 0.16.0 functional
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://api.usesaferoute.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.usesaferoute.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| usesaferoute.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.usesaferoute.com/mcp | Unreachable | ||
| http (plaintext) | http://api.usesaferoute.com/mcp | HTTPS enforced |
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 →
check_base_swap ~81
Wallet-free approved-token Base swap safety preflight. Costs $0.001 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| discoverySource | string | – | – |
| from | string | yes | – |
| intentId | string | – | – |
| referralCode | string | – | – |
| sourceAgentId | string | – | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
check_token_risk ~58
Approved Base token risk and liquidity check. Costs $0.03 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | – | – |
| referralCode | string | – | – |
| sourceAgentId | string | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
check_wallet_risk ~59
Read-only Base wallet account-posture check. Costs $0.01 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | – | – |
| referralCode | string | – | – |
| sourceAgentId | string | – | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
get_safe_swap_quote ~104
Safety-checked noncustodial Base swap quote. Costs $0.01 USDC; the buyer signs and broadcasts.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| discoverySource | string | – | – |
| executionMode | string | – | – |
| from | string | yes | – |
| intentId | string | – | – |
| referralCode | string | – | – |
| sourceAgentId | string | – | – |
| to | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
guard_base_trade ~89
Complete pre-sign trade guard with route and simulation evidence. Costs $0.12 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| executionMode | string | – | – |
| from | string | yes | – |
| intentId | string | – | – |
| referralCode | string | – | – |
| sourceAgentId | string | – | – |
| to | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
list_supported_assets ~28
List SafeRoute's seven approved Base assets, limits, fees, and execution modes. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preflight_transaction ~70
Decode and simulate approved Base ERC-20 calldata or SafeRoute's exact official ERC-8004 registration. Costs $0.05 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| intentId | string | – | – |
| referralCode | string | – | – |
| sourceAgentId | string | – | – |
| transaction | object | yes | – |
No output schema declared.
No examples provided.
prepare_token_transfer ~80
Prepare a bounded, simulated unsigned Base token transfer. Costs $0.10 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| intentId | string | – | – |
| recipient | string | yes | – |
| referralCode | string | – | – |
| sender | string | yes | – |
| sourceAgentId | string | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
protect_payment ~77
One automatic x402 payment-safety front door: pre-payment ALLOW/BLOCK, duplicate-safe ID binding, policy risk reasons, and optional mined-settlement verification. Free and rate-limited; the buyer signs and pays.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | – |
| payment | object | yes | – |
| settlement | object | – | – |
No output schema declared.
No examples provided.
prove_safe_action ~113
Create a signed pre-sign ALLOW, BLOCK, or REVIEW receipt. Costs $0.05 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| amount | string | – | – |
| executionMode | string | – | – |
| from | string | – | – |
| intentId | string | – | – |
| referralCode | string | – | – |
| sourceAgentId | string | – | – |
| to | string | – | – |
| token | string | – | – |
| transaction | object | – | – |
| wallet | string | – | – |
No output schema declared.
No examples provided.
route_agent_payment ~60
Prepare a bounded, simulated exact-buy route to a payer-owned Base USDC target covering the x402 payment and optional buffer. Costs $0.05 USDC; buyer confirms funding, then retries standard x402 once.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | – |
No output schema declared.
No examples provided.
verify_swap_execution ~52
Verify a standard-mode SafeRoute Base execution against its signed receipt. Free; referral payouts remain disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | – |
| receiptSignature | string | yes | – |
| transactionHash | string | yes | – |
No output schema declared.
No examples provided.
verify_transaction_intent ~67
Compare a mined Base transaction with buyer intent. Costs $0.05 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | object | yes | – |
| intentId | string | – | – |
| referralCode | string | – | – |
| sourceAgentId | string | – | – |
| transactionHash | string | yes | – |
No output schema declared.
No examples provided.
How do I install the SafeRoute MCP server?
SafeRoute is a hosted endpoint at https://api.usesaferoute.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 · api.usesaferoute.com
claude mcp add --transport http crystalsignal-saferoute 'https://api.usesaferoute.com/mcp'
What is the SafeRoute MCP server?
SafeRoute is an MCP server listed in the public MCP registry as io.github.crystalsignal/saferoute. Noncustodial Base x402 payment control and seller settlement recovery. This page covers its hosted endpoint (https://api.usesaferoute.com/mcp).
Is the SafeRoute MCP server safe to use?
SafeRoute scores 70 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 SafeRoute MCP server expose?
SafeRoute exposes 13 tools: protect_payment, check_base_swap, get_safe_swap_quote, prove_safe_action, check_wallet_risk, and 8 more. Their descriptions and schemas cost roughly 938 tokens of context every time the server is loaded.
Does the SafeRoute MCP server require authentication?
Its publisher declares no required credentials for SafeRoute. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the SafeRoute MCP server still maintained?
SafeRoute is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.