xyz.routheus/routheus
REMOTE · ROUTHEUS.XYZ · SCANNED SEP 20
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 → Why this is hard to 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 Usability79
- AI-judged instruction clarity (excellent).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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the xyz.routheus/routheus MCP server?
xyz.routheus/routheus is a hosted endpoint at https://routheus.xyz/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 · routheus.xyz
claude mcp add --transport http xyz-routheus-routheus 'https://routheus.xyz/mcp'
{
"mcpServers": {
"xyz-routheus-routheus": {
"url": "https://routheus.xyz/mcp"
}
}
} {
"servers": {
"xyz-routheus-routheus": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://routheus.xyz/mcp"
}
}
} assistant mcp add xyz-routheus-routheus -t streamable-http -u '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.
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 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
- 30 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
- 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 0
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 20 Sept 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 | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 28e19cf8856f60be1307466df1bb89b2 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. 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 →
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.
What is the xyz.routheus/routheus MCP server?
xyz.routheus/routheus is an MCP server listed in the public MCP registry as xyz.routheus/routheus. Multichain DEX router: free MCP tools for swap-quote prices, chains, catalog; paid via x402. This page covers its hosted endpoint (https://routheus.xyz/mcp).
Is the xyz.routheus/routheus MCP server safe to use?
xyz.routheus/routheus scores 79 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 xyz.routheus/routheus MCP server expose?
xyz.routheus/routheus exposes 3 tools: routheus_catalog, routheus_chains, routheus_price_offer. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.
Does the xyz.routheus/routheus MCP server require authentication?
No. We connected to xyz.routheus/routheus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the xyz.routheus/routheus MCP server still maintained?
xyz.routheus/routheus is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.