Connect Routavo and your agent gets 4 tools, among them call, discover, dispute. It answers at https://routavo.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Any API, four tools: discover, call with routing and signed receipts, verify, dispute.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
call | 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 choi Inputs: provider, capability, arguments, max_price, max_latency_ms, dry_run |
discover | 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 thi Inputs: capability, query |
dispute | 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. Inputs: receipt, reason |
verify | 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. Inputs: receipt |
Every block below points at https://routavo.com/api/mcp. Pick your client and copy.
claude mcp add --transport http routavo https://routavo.com/api/mcp
{
"mcpServers": {
"routavo": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://routavo.com/api/mcp"]
}
}
}{
"mcpServers": {
"routavo": {
"url": "https://routavo.com/api/mcp"
}
}
}{
"servers": {
"routavo": {
"type": "http",
"url": "https://routavo.com/api/mcp"
}
}
}{
"context_servers": {
"routavo": {
"url": "https://routavo.com/api/mcp"
}
}
}{
"mcpServers": {
"routavo": {
"serverUrl": "https://routavo.com/api/mcp"
}
}
}{
"mcpServers": {
"routavo": {
"url": "https://routavo.com/api/mcp"
}
}
}name: Routavo
version: 0.0.1
schema: v1
mcpServers:
- name: Routavo
type: streamable-http
url: https://routavo.com/api/mcp{
"mcpServers": {
"routavo": {
"httpUrl": "https://routavo.com/api/mcp"
}
}
}{
"mcpServers": {
"routavo": {
"type": "http",
"url": "https://routavo.com/api/mcp"
}
}
}{
"mcpServers": {
"routavo": {
"url": "https://routavo.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Froutavo.com%2Fapi%2Fmcp&type=streamable_http&id=routavo&name=Routavo
It answered our last check on 19 October 2026 in 217 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by routavo.com and served from routavo.com, the vendor's own domain: https://routavo.com/api/mcp.
4, as returned by the server's own tools/list on 11 September 2026: call, discover, dispute, verify.
It answered our last check on 19 October 2026 in 217 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://routavo.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.routavo. Endpoint host: routavo.com. ARD identifier: urn:air:com.routavo:mcp:routavo.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.