83trust / 100

Routavo

by routavo.com in Security & trust

MCP serverPassing, checked 7 h ago

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

https://routavo.com/api/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
223 ms typical, 223 ms slowest 5%
Last check
7 h ago
Next check
any minute now

How to call it

Add it to any MCP client that supports remote servers.

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

4 tools

  • 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 this before call() when you do not already

  • 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 choice. Failed calls are recorded but cost n

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

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

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
7 h agoPassed200254 ms
15 h agoPassed200223 ms