# Routavo (remote · routavo.com)

Any API, four tools: discover, call with routing and signed receipts, verify, dispute.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `routavo.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-routavo-routavo/api-mcp.md), [page](https://verifymcp.io/servers/com-routavo-routavo/api-mcp)

## Channel facts

- Endpoint: `https://routavo.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.17.9`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (25% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-routavo-routavo 'https://routavo.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-routavo-routavo": {
      "url": "https://routavo.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-routavo-routavo": {
      "type": "http",
      "url": "https://routavo.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-routavo-routavo]
url = "https://routavo.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-routavo-routavo": {
      "type": "remote",
      "url": "https://routavo.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-routavo-routavo --url 'https://routavo.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-routavo-routavo:
    url: "https://routavo.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-routavo-routavo": {
      "Transport": "http",
      "Url": "https://routavo.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-routavo-routavo -t streamable-http -u 'https://routavo.com/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 75, +1)

- [functional] Server version: 0.17.3 → 0.17.9

### 2026-09-22 (score 74, 0)

- [functional] Server version: 0.17.2 → 0.17.3

### 2026-09-21 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.15.0 → 0.17.2
- [cosmetic] “call” added an optional parameter “country”

### 2026-09-20 (score 74, +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.

### 2026-09-18 (score 73, +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.

### 2026-09-16 (score 72, +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.

### 2026-09-14 (score 71, +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.

## MCP tools (4)

### `discover` (~149 tokens)

Discover APIs

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.

Input parameters:

- `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…

Output parameters:

- `count` (integer)
- `providers` (array)
- `routing` (object)

### `call` (~988 tokens)

Call an API

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.

Input parameters:

- `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.

### `verify` (~71 tokens)

Verify a receipt

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.

Input parameters:

- `receipt` (object, required): The receipt object from a call() result.

### `dispute` (~102 tokens)

Dispute a charge

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.

Input parameters:

- `reason` (string, required): What was wrong, in plain words. Up to 500 characters. Do not paste the response body.
- `receipt` (object, required): The receipt object from the call() result you are disputing.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-routavo-routavo/api-mcp#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 74
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://routavo.com/api/mcp
- Website: https://routavo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-routavo-routavo/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-routavo-routavo/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-routavo-routavo/api-mcp