xyz.routheus/routheus
REMOTE · ROUTHEUS.XYZ · SCANNED AUG 3
Multichain DEX router: free MCP tools for swap-quote prices, chains, catalog; paid via x402.
Available components
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 →
Endpoint Security60
- 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 3 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 413 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · routheus.xyz
claude mcp add --transport http xyz-routheus-routheus https://routheus.xyz/mcp
[mcp_servers.xyz-routheus-routheus] url = "https://routheus.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-routheus-routheus": {
"type": "remote",
"url": "https://routheus.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-routheus-routheus --url https://routheus.xyz/mcp --transport streamable-http
mcp_servers:
xyz-routheus-routheus:
url: "https://routheus.xyz/mcp" {
"mcpServers": {
"xyz-routheus-routheus": {
"type": "http",
"url": "https://routheus.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 63
First indexed and scored.
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 3 Aug 2026 · Probed https://routheus.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=routheus.xyz | CN=WE1,O=Google Trust Services,C=US | 11 Jul 2026 | 9 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 1c6af43168e7da7f0e1093116849df2d |
| SANs: routheus.xyz, *.routheus.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC secure
Validation of routheus.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| routheus.xyz. | present | 2371 | 13 | Verified |
| routheus.xyz. | Verified address RRset verified with the apex keys |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://routheus.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://routheus.xyz/mcp | HTTPS enforced | 301 | https://routheus.xyz/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.
routheus_catalog ~93
Get the live Routheus product catalog: DEX endpoints, the FREE tier (single-input swap quotes and quote+calldata are free, rate-limited per IP — no payment or key), per-call USDC prices for paid products, supported EVM chains, x402 payment details, and a contact email for custom/higher-limit plans. Call this first to learn what's available, what's free, and what costs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
routheus_chains ~49
List the DEX chains Routheus can quote on, with accepted path aliases (canonical slug, chain name, or EIP-155 id — e.g. eth = ethereum = 1).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
routheus_price_offer ~132
Get the price for a specific product, WITHOUT paying. For quote and quote_calldata it reports that a rate-limited FREE tier exists (call the returned URL with no X-PAYMENT header to use it); for all products it returns the exact x402 USDC offer and the ready-to-call HTTP URL. To get paid data, call that URL with an x402 client (x402-fetch / @x402/fetch / AgentKit).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain slug/name/id, e.g. base, ethereum, 1 |
| product | string | yes | Which product to price |
No output schema declared.
No examples provided.