# Revolist Revogrid MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.revolist%2Frevogrid-mcp
Registry id: `mcp-registry/io.github.revolist/revogrid-mcp`
Status: live (checked 2026-10-27T07:17:19.319Z)

## Verdict

Revolist Revogrid MCP server answered 99.9% of Glimind's liveness checks over 30 days, better than 29% of MCP servers, with 642 ms median handshake and 2 outages in 90 days. Its agent-readiness grade is A (95/100) across 8 tools, costing an agent about 2,537 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.9% | 29% of MCP servers |
| Median handshake latency | 642 ms | 35% of MCP servers |
| p95 handshake latency | 3159 ms | — |
| Checks in 30 days | 5,033 | — |
| Outages, 90 days | 2 | — |
| Median recovery | 60 min | — |
| Agent-readiness score | 95/100 (A) | 79% of MCP servers |
| Tools | 8 | — |
| Tool-list size for an agent | ~2,537 tokens | 49% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "revolist-revogrid-mcp-server": {
      "type": "http",
      "url": "https://mcp.rv-grid.com"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http revolist-revogrid-mcp-server https://mcp.rv-grid.com
```

## Tools (8)

- `find_examples`: Use when implementation evidence should be a runnable or registered RevoGrid example, optionally filtered by framework and package.
- `get_migration_notes`: Get upgrade notes between RevoGrid versions.
- `inspect_revogrid_api`: Use after discovery to resolve one exact symbol or capability. Returns ambiguity candidates instead of guessing and includes its supported import and evidence.
- `list_revogrid_capabilities`: Start here to discover supported public capabilities and package ownership. Returns compact paginated summaries linked to detailed resources.
- `plan_revogrid_implementation`: Use after resolving capability names to compose a deterministic package, plugin-order, configuration, lifecycle, and compatibility blueprint.
- `resolve_feature_matrix`: Resolve whether a RevoGrid feature exists, whether it is Pro, and where to learn it.
- `search_revogrid_docs`: Use for broad RevoGrid questions or when the exact API name is unknown. Searches source-grounded docs and API evidence; defaults to public exports.
- `validate_revogrid_usage`: Use before implementation handoff to statically check structured RevoGrid imports, configuration, dependencies, versions, and optional bounded source. Never exe

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.