Is the Routavo MCP server down?

mcp-registry/com.routavo/routavo · v0.29.2

As of 2026-10-22 09:42 UTC, the Routavo MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

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

claude mcp add --transport http routavo-mcp-server https://routavo.com/api/mcp

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (82/100)

What to fix (3)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.routavo%2Froutavo/fixes

{
  "name": "dispute",
  "description": "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.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Dispute a charge"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.routavo/routavo"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.routavo/routavo"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.95% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• call ~1,435 tokens
• discover ~222 tokens
• dispute ~179 tokens
• verify ~132 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.routavo%2Froutavo.svg)](https://glimind.com/server/mcp-registry%2Fcom.routavo%2Froutavo?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.routavo%2Froutavo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.routavo%2Froutavo.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.routavo%2Froutavo.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.routavo%2Froutavo?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:255633feb24e8108…, first seen 2026-10-17, included at leaf 1600 of 45,218. Version history · verify what your client received.

Tools (4)

• call
• discover
• dispute
• verify

Compare: most reliable communication servers · most reliable knowledge servers · most reliable other servers · most reliable security servers

claude mcp add --transport http glimind https://glimind.com/mcp

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

FAQ

Is the Routavo MCP server down right now?

As of 2026-10-22 09:42 UTC, the Routavo MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Routavo MCP server provide?

Routavo MCP server advertises 4 tools, including call, discover, dispute, verify.

How do I install Routavo MCP server?

Point your MCP client at this streamable-http endpoint: https://routavo.com/api/mcp

Is the Routavo MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Routavo MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.