API Tools

routavo.com

Discovers and routes API calls on the Routavo network with metering and verification.

1 endpoint4 known toolsFirst detected September 4, 2026Last detected September 4, 2026

ENDPOINT 1

https://routavo.com/api/mcp

No auth detected

MCP server metadata

Name: routavo
Version: 0.10.0

Capabilities

tools

Server instructions

Routavo routes agent calls to APIs and meters them. Call discover() to see what the network can do and how Routavo picks between providers, then call() to use it. This build meters only: prices are quoted but nothing settles.

Known tools 4

discover

Find APIs on the Routavo network that can perform a capability.

Inferred read-only

call

Route a call to the Routavo network, meter it, and return the result.

Inferred read-only

verify

Check a receipt returned by call().

Inferred read-only

dispute

Flag a metered call for the provider to review.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.routavo]
url = "https://routavo.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "routavo": {
      "type": "http",
      "url": "https://routavo.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: routavo
Remote MCP URL: https://routavo.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "routavo",
  "transport": "streamable-http",
  "url": "https://routavo.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.