Koskamo

Routavo MCP

An MCP server operated by Routavo that provides AI agents with access to public data tools including weather forecasts, geocoding, earthquakes, elevation, exchange rates, public holidays, SEC filings, Wikipedia summaries, and weather alerts. It features four tools: discover, call, verify, and dispute, supporting per-call payments via x402 or USDC balance without requiring an account for the free tier.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Routavo MCP logo, by RoutavoVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Routavo
MCP endpoint (Streamable HTTP)
https://routavo.com/api/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (4)

4 of 4 have a description · 0 of 4 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to routavo.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve weather forecasts for specific locations
  • Perform geocoding and reverse geocoding
  • Access public data like SEC filings and Wikipedia summaries
  • Verify payment receipts for API calls

Source and maintenance

Vendor evidenceRegistry 0.17.9

Protocol and capabilities

Server
routavo 0.29.6
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

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. Calls are paid from a balance: top up with a card at /topup, or deposit USDC after proving a wallet at /api/wallet, or send an x402 authorization; without any of those you are on a small free tier.

Tools

4 advertised

discover — Discover APIs
Advertised by the server during the last successful anonymous check.

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 know a provider id.

discover input schema
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free text when you do not know the capability name, e.g. \"turn an address into coordinates\" or \"will it rain tomorrow\". Matched against names, aliases, tags and descriptions; results come back ranked with a score."
    },
    "capability": {
      "type": "string",
      "description": "What you need done, e.g. \"geocode\" or \"forecast\". Omit to list everything."
    }
  },
  "additionalProperties": false
}
discover output schema
{
  "type": "object",
  "required": [
    "providers",
    "count",
    "routing"
  ],
  "properties": {
    "count": {
      "type": "integer"
    },
    "routing": {
      "type": "object"
    },
    "providers": {
      "type": "array",
      "items": {
        "type": "object"
      }
    }
  }
}
call — Call an API
Advertised by the server during the last successful anonymous check.

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

call input schema
{
  "type": "object",
  "properties": {
    "plan": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "maxItems": 8,
      "description": "Instead of one call, a sequence of up to 8 steps: [{ id, capability | provider, arguments, max_price?, max_latency_ms? }]. A later step may take a value from an earlier one with { \"$ref\": \"<step id>.output.<path>\" }, e.g. { \"$ref\": \"geo.output.results[0].lat\" }. The whole plan is quoted before anything runs; with dry_run it is only quoted. Steps run in order and stop at the first failure. Each step returns its own receipt and the response carries one total."
    },
    "batch": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "maxItems": 50,
      "description": "Instead of one arguments object, up to 50 of them for the same capability or provider. Run in parallel, each with its own receipt, one total. Failed items cost nothing and do not stop the others."
    },
    "budget": {
      "type": "object",
      "properties": {
        "id": {
          "type": "string"
        },
        "max": {
          "type": "string"
        },
        "statement": {
          "type": "boolean"
        }
      },
      "description": "A task budget: { id, max }. Spend under this id is tracked across any number of calls, plans and batches, and a call that would take it past max is refused with code \"budget\". { id, statement: true } returns what the budget has spent and the receipts behind it.",
      "additionalProperties": false
    },
    "fields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Return only these output paths, e.g. [\"results.name\", \"results.lat\", \"results.lng\"]. Saves tokens; the receipt still hashes the full answer."
    },
    "quorum": {
      "type": "integer",
      "maximum": 3,
      "minimum": 2,
      "description": "Ask 2 or 3 providers the same question and get an agreement score with every answer. Each provider is charged. Refused if fewer providers clear your constraints, so quote it first with dry_run."
    },
    "recipe": {
      "type": "string",
      "description": "A named, published plan, e.g. \"weather_for_place\". Give its arguments and it runs the steps for you, quoted first, with the last step's output on top. discover() lists recipes with their inputs and estimated price."
    },
    "wallet": {
      "type": "string",
      "description": "Your wallet address, asserted. Attributes metering and a daily cap on the free tier; it proves nothing. To pay from a balance, prove the wallet once at /api/wallet and send the key it returns as wallet_key or as Authorization: Bearer rw_...",
      "x-mcp-header": "Wallet"
    },
    "country": {
      "type": "string",
      "description": "Two letter code for where this request is, e.g. \"FR\". A routing hint, not an argument to the API: it lets a provider that covers only that country be chosen, and keeps one that does not out of the running. Unnecessary when the arguments already carry coordinates."
    },
    "dry_run": {
      "type": "boolean",
      "description": "Quote only: which provider would be chosen, at what price, with what latency, and why. Nothing is called, charged or counted."
    },
    "payment": {
      "type": "object",
      "properties": {
        "rail": {
          "type": "string"
        },
        "payload": {
          "type": "object"
        }
      },
      "description": "Pay this one call with x402: { rail: \"x402\", payload: <PaymentPayload> }, an EIP-3009 authorization to the pay-to address for at least the price, signed by your wallet. The requirements to sign are in discover() and in any payment_required error. A facilitator verifies and settles it; the receipt carries the transaction.",
      "additionalProperties": false
    },
    "failover": {
      "type": "boolean",
      "description": "Default true when routing by capability: if the chosen provider fails, the next eligible one is tried and only the one that answered is charged. Set false to fail fast."
    },
    "provider": {
      "type": "string",
      "description": "Provider id, e.g. \"open-meteo.geocode\". Omit to route by capability.",
      "x-mcp-header": "Provider"
    },
    "arguments": {
      "type": "object",
      "description": "Arguments in the capability contract shape from discover(). Learn geocode once; every provider behind it takes the same input and returns the same output.",
      "additionalProperties": true
    },
    "max_price": {
      "type": "string",
      "description": "Do not route above this price per call, e.g. \"0.0030\""
    },
    "max_total": {
      "type": "string",
      "description": "For a plan: do not run if the quoted total exceeds this, e.g. \"0.0100\"."
    },
    "capability": {
      "type": "string",
      "description": "Capability to route on, e.g. \"geocode\". Ignored when provider is given."
    },
    "wallet_key": {
      "type": "string",
      "description": "A wallet key (rw_...) from /api/wallet. Proves the wallet, and calls are paid from its deposited USDC balance. Prefer sending it as the Authorization: Bearer header."
    },
    "max_latency_ms": {
      "type": "integer",
      "description": "Do not route to a provider slower than this p50"
    },
    "idempotency_key": {
      "type": "string",
      "description": "Your own id for this call, up to 64 characters. A retry with the same key within 24 hours returns the same result and receipt and is never charged again. The output is kept for those 24 hours only because you asked for replay."
    }
  },
  "additionalProperties": false
}
verify — Verify a receipt
Advertised by the server during the last successful anonymous check.

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.

verify input schema
{
  "type": "object",
  "required": [
    "receipt"
  ],
  "properties": {
    "receipt": {
      "type": "object",
      "description": "The receipt object from a call() result.",
      "additionalProperties": true
    }
  },
  "additionalProperties": false
}
dispute — Dispute a charge
Advertised by the server during the last successful anonymous check.

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.

dispute input schema
{
  "type": "object",
  "required": [
    "receipt",
    "reason"
  ],
  "properties": {
    "reason": {
      "type": "string",
      "description": "What was wrong, in plain words. Up to 500 characters. Do not paste the response body."
    },
    "receipt": {
      "type": "object",
      "description": "The receipt object from the call() result you are disputing.",
      "additionalProperties": true
    }
  },
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
521 ms
95th percentile latency
521 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 521 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http routavo-mcp https://routavo.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add routavo-mcp --url https://routavo.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable routavo-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "routavo-mcp": {
      "url": "https://routavo.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "routavo-mcp": {
      "type": "streamableHttp",
      "url": "https://routavo.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start routavo-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "routavo-mcp": {
      "type": "http",
      "url": "https://routavo.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http routavo-mcp https://routavo.com/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://routavo.com/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "routavo-mcp": {
      "serverUrl": "https://routavo.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Routavo MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Routavo MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing