Any API, four tools: discover, call with routing and signed receipts, verify, dispute.
Connect Remote server
claude mcp add --transport http routavo https://routavo.com/api/mcp
{
"mcpServers": {
"routavo": {
"url": "https://routavo.com/api/mcp"
}
}
}
{
"servers": {
"routavo": {
"type": "http",
"url": "https://routavo.com/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://routavo.com/api/mcp
Tools 4 found in our last check
discoverFind 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…
callRoute 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…
verifyCheck 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.
disputeFlag 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.
Details
| Endpoint | https://routavo.com/api/mcp (Streamable HTTP) |
| First published | 23 Sep 2026 |
| Last updated | 23 Sep 2026 |
| Registry name | com.routavo/routavo |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
