# Renkeimap Info MCP server

Source: https://glimind.com/server/mcp-registry%2Fjp.renkeimap%2Frenkeimap-info
Registry id: `mcp-registry/jp.renkeimap/renkeimap-info`
Status: live (checked 2026-10-27T08:13:18.460Z)

## Verdict

Renkeimap Info MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 1305 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (91/100) across 10 tools, costing an agent about 1,553 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 1305 ms | 11% of MCP servers |
| p95 handshake latency | 3800 ms | — |
| Checks in 30 days | 5,045 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 91/100 (A) | 70% of MCP servers |
| Tools | 10 | — |
| Tool-list size for an agent | ~1,553 tokens | 57% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "renkeimap-info-mcp-server": {
      "type": "http",
      "url": "https://renkeimap.jp/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http renkeimap-info-mcp-server https://renkeimap.jp/mcp
```

## Tools (10)

- `renkeimap_brief`: One round trip = renkeimap_find_system + renkeimap_status + renkeimap_hintpack. Give a slug or the system name as the user wrote it; same shapes as the single t
- `renkeimap_compare`: Side-by-side comparison of 2-5 published systems/tools on the same ledger items (API, contract, price, rate limit, data location, exit, security…). Each cell = 
- `renkeimap_connect`: Routes INTO one system, most stable first: (1) the vendor's official MCP server — URL/auth/local command verbatim, with source and date (never a URL found by se
- `renkeimap_find_system`: Search published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive. ≤10 each.
- `renkeimap_hintpack`: Static public knowledge for one system: what its vendor error messages mean, official support/contact URLs, login method shape. Sourced from public vendor pages
- `renkeimap_pair`: Whether and how two systems can exchange data: per-method verdicts (official API / CSV / screen-fill) measured from public primary sources, plus measured field-
- `renkeimap_plan`: One call to connect or move data between two systems: route states (API/CSV/screen) + legend, each side's best official route (vendor MCP URL verbatim — never o
- `renkeimap_status`: Status of one system observed EXTERNALLY by IT連携マップ (third party, not the vendor): conclusion, vendor notices (verbatim title+URL), editor's check, 1h user repo
- `renkeimap_status_history`: Vendor-published incident history and announced maintenance for one system, checked word for word (the vendor's own records, not our observation): counts, month
- `renkeimap_system_facts`: First-hand, survey-dated facts about one system (auth method, rate limits, CSV surfaces, pricing pages — tags + editorial summaries with sources). Every respons

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