Routavo
REMOTE · ROUTAVO.COM · SCANNED SEP 25
Any API, four tools: discover, call with routing and signed receipts, verify, dispute.
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 Security66
- 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 4 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1399 tokens (~349/item across 4 items; 4 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 Management70
- Stability observed for 21 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
- Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Routavo MCP server?
Routavo is a hosted endpoint at https://routavo.com/api/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 · routavo.com
claude mcp add --transport http com-routavo-routavo 'https://routavo.com/api/mcp'
{
"mcpServers": {
"com-routavo-routavo": {
"url": "https://routavo.com/api/mcp"
}
}
} {
"servers": {
"com-routavo-routavo": {
"type": "http",
"url": "https://routavo.com/api/mcp"
}
}
} [mcp_servers.com-routavo-routavo] url = "https://routavo.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-routavo-routavo": {
"type": "remote",
"url": "https://routavo.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-routavo-routavo --url 'https://routavo.com/api/mcp' --transport streamable-http
mcp_servers:
com-routavo-routavo:
url: "https://routavo.com/api/mcp" {
"McpServers": {
"com-routavo-routavo": {
"Transport": "http",
"Url": "https://routavo.com/api/mcp"
}
}
} assistant mcp add com-routavo-routavo -t streamable-http -u 'https://routavo.com/api/mcp'
{
"mcpServers": {
"com-routavo-routavo": {
"type": "http",
"url": "https://routavo.com/api/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.
- 25 Sept 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
- 23 Sept 26 +1
- Server version: 0.17.3 → 0.17.9 functional
- 22 Sept 26 0
- Server version: 0.17.2 → 0.17.3 functional
- 21 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.15.0 → 0.17.2 functional
- “call” added an optional parameter “country” cosmetic
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Probed https://routavo.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=routavo.com | CN=YR1,O=Let's Encrypt,C=US | 17 Aug 2026 | 15 Nov 2026 | RSA 2048 | SHA256-RSA | 52981799332c901743e3b739c8d5a34a154 |
| SANs: routavo.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of routavo.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| routavo.com. | present | 2512 | 8 | Verified |
| routavo.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://routavo.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://routavo.com/api/mcp | HTTPS enforced | 308 | https://routavo.com/api/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 →
call Call an API ~988
Route a call to the Routavo network, meter it, and return the result. Give either a provider id from discover(), or a capability and let Routavo pick using its published routing rule. Optional max_price and max_latency_ms constrain the choice. Failed calls are recorded but cost nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Arguments in the capability contract shape from discover(). Learn geocode once; every provider behind it takes the same input and returns the same output. |
| batch | array | – | Instead of one arguments object, up to 50 of them for the same capability or provider. Run in parallel, each with its own receipt, one total. Failed items cost nothing and do not stop the others. |
| budget | object | – | A task budget: { id, max }. Spend under this id is tracked across any number of calls, plans and batches, and a call that would take it past max is refused with code "budget". { id, statement: true }… |
| capability | string | – | Capability to route on, e.g. "geocode". Ignored when provider is given. |
| country | string | – | Two letter code for where this request is, e.g. "FR". A routing hint, not an argument to the API: it lets a provider that covers only that country be chosen, and keeps one that does not out of the ru… |
| dry_run | boolean | – | Quote only: which provider would be chosen, at what price, with what latency, and why. Nothing is called, charged or counted. |
| failover | boolean | – | Default true when routing by capability: if the chosen provider fails, the next eligible one is tried and only the one that answered is charged. Set false to fail fast. |
| fields | array | – | Return only these output paths, e.g. ["results.name", "results.lat", "results.lng"]. Saves tokens; the receipt still hashes the full answer. |
| idempotency_key | string | – | Your own id for this call, up to 64 characters. A retry with the same key within 24 hours returns the same result and receipt and is never charged again. The output is kept for those 24 hours only be… |
| max_latency_ms | integer | – | Do not route to a provider slower than this p50 |
| max_price | string | – | Do not route above this price per call, e.g. "0.0030" |
| max_total | string | – | For a plan: do not run if the quoted total exceeds this, e.g. "0.0100". |
| payment | object | – | Pay this one call with x402: { rail: "x402", payload: <PaymentPayload> }, an EIP-3009 authorization to the pay-to address for at least the price, signed by your wallet. The requirements to sign are i… |
| plan | array | – | Instead of one call, a sequence of up to 8 steps: [{ id, capability | provider, arguments, max_price?, max_latency_ms? }]. A later step may take a value from an earlier one with { "$ref": "<step id>.… |
| provider | string | – | Provider id, e.g. "open-meteo.geocode". Omit to route by capability. |
| quorum | integer | – | Ask 2 or 3 providers the same question and get an agreement score with every answer. Each provider is charged. Refused if fewer providers clear your constraints, so quote it first with dry_run. |
| recipe | string | – | A named, published plan, e.g. "weather_for_place". Give its arguments and it runs the steps for you, quoted first, with the last step's output on top. discover() lists recipes with their inputs and e… |
| wallet | string | – | Your wallet address, asserted. Attributes metering and a daily cap on the free tier; it proves nothing. To pay from a balance, prove the wallet once at /api/wallet and send the key it returns as wall… |
| wallet_key | string | – | A wallet key (rw_...) from /api/wallet. Proves the wallet, and calls are paid from its deposited USDC balance. Prefer sending it as the Authorization: Bearer header. |
No output schema declared.
No examples provided.
discover Discover APIs ~149
Find APIs on the Routavo network that can perform a capability. Returns each provider with its published price, measured latency, terms, and the exact argument schema for calling it, plus the rule Routavo uses to pick between them. Call this before call() when you do not already know a provider id.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | What you need done, e.g. "geocode" or "forecast". Omit to list everything. |
| query | string | – | Free text when you do not know the capability name, e.g. "turn an address into coordinates" or "will it rain tomorrow". Matched against names, aliases, tags and descriptions; results come back ranked… |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| providers | array | yes | – |
| routing | object | yes | – |
No examples provided.
dispute Dispute a charge ~102
Flag a metered call for the provider to review. Takes the receipt and a short reason. The receipt must verify and must have charged something. The dispute lands in that provider's queue and is visible to Routavo. One dispute per receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | yes | What was wrong, in plain words. Up to 500 characters. Do not paste the response body. |
| receipt | object | yes | The receipt object from the call() result you are disputing. |
No output schema declared.
No examples provided.
verify Verify a receipt ~71
Check a receipt returned by call(). Confirms the signature, so the provider, price, fee, and the hashes of what went in and came out are exactly what Routavo recorded. Works for anyone holding the receipt. Reveals nothing else.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | The receipt object from a call() result. |
No output schema declared.
No examples provided.
What is the Routavo MCP server?
Routavo is an MCP server listed in the public MCP registry as com.routavo/routavo. Any API, four tools: discover, call with routing and signed receipts, verify, dispute. This page covers its hosted endpoint (https://routavo.com/api/mcp).
Is the Routavo MCP server safe to use?
Routavo scores 76 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 Routavo MCP server expose?
Routavo exposes 4 tools: discover, call, verify, dispute. Their descriptions and schemas cost roughly 1,310 tokens of context every time the server is loaded.
Does the Routavo MCP server require authentication?
No. We connected to Routavo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Routavo MCP server still maintained?
Routavo is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.