Routavo MCP server

• Registry namecom.routavo/routavoverified in the MCP registry

The registry name sits under routavo.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-25
• Tools4
• Server calls itselfroutavo
• Server version0.29.6
• Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 86 ms.

• Its tools do none of the product's use cases we checked: measure how often AI assistants name your API; rewrite docs so agents know when to use it.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer232 ms
• Space in an agent's context≈ 1,771 tokensthe definitions of all its tools (4), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results1 of 4 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 4 of 4

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

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

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

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