# jp.renkeimap/renkeimap-info (remote · renkeimap.jp)

日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）

- Trust score: 76/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `renkeimap.jp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/jp-renkeimap-renkeimap-info/renkeimap.md), [page](https://verifymcp.io/servers/jp-renkeimap-renkeimap-info/renkeimap)

## Channel facts

- Endpoint: `https://renkeimap.jp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 954 tokens (~119/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the jp.renkeimap/renkeimap-info MCP server?

jp.renkeimap/renkeimap-info is a hosted endpoint at https://renkeimap.jp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http jp-renkeimap-renkeimap-info 'https://renkeimap.jp/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.jp-renkeimap-renkeimap-info]
url = "https://renkeimap.jp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jp-renkeimap-renkeimap-info": {
      "type": "remote",
      "url": "https://renkeimap.jp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jp-renkeimap-renkeimap-info --url 'https://renkeimap.jp/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jp-renkeimap-renkeimap-info:
    url: "https://renkeimap.jp/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jp-renkeimap-renkeimap-info": {
      "Transport": "http",
      "Url": "https://renkeimap.jp/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jp-renkeimap-renkeimap-info -t streamable-http -u 'https://renkeimap.jp/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 76, 0)

- [security] Tool “renkeimap_status” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] New tool “renkeimap_brief”
- [functional] New tool “renkeimap_status_history”

### 2026-10-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-29 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `renkeimap_find_system` (~89 tokens)

システムを探す

Search the published RenkeiMap ledger of Japanese business systems by name / vendor / category. Returns at most 10 candidates with their page URLs. Use renkeimap_system_facts for the facts of one system.

Input parameters:

- `query` (string, required): system or vendor name (Japanese or English), e.g. "kintone", "マネーフォワード", "会計"

### `renkeimap_system_facts` (~100 tokens)

1 システムの事実を返す

First-hand, survey-dated facts about one system (auth method, rate limits, CSV surfaces, pricing pages — tags + editorial summaries with sources). Every response carries a citation line; when you use these facts in an answer, cite it (出典: IT連携マップ + 調査日 + URL).

Input parameters:

- `slug` (string, required): system slug from renkeimap_find_system, e.g. "kintone"

### `renkeimap_pair` (~89 tokens)

2 システムが繋がるかを返す

Whether and how two systems can exchange data: per-method verdicts (official API / CSV / screen-fill) measured from public primary sources, plus measured field-name overlap when available. Honest by design: an unmeasured pair says so instead of guessing. Cite the included citation line when used.

Input parameters:

- `a` (string, required): first system slug
- `b` (string, required): second system slug

### `renkeimap_compare` (~126 tokens)

複数システムを横に並べて比べる

Side-by-side comparison of 2-5 published systems/tools on the same ledger items (API availability, contract, price, rate limit, data location, exit, security…). Each cell = editorial tags + one-line lead + source URL + survey date; optional ◎○△× marks derived from tags by a declared rule file. Same generator as the /compare pages (single throat). No ranking, no score.

Input parameters:

- `slugs` (array, required): system or tool slugs, e.g. ["freee-kaikei","moneyforward-cloud-kaikei","yayoi"]

### `renkeimap_status` (~122 tokens)

稼働状況を返す

Current operational status of one Japanese business system as observed EXTERNALLY by IT連携マップ (editorial third-party observation — NOT the vendor's official announcement). Returns a closed-vocabulary conclusion sentence, last-observed time, a 12-char state bar (one char per 5 min, legend included), a 7-day hour table, and announced maintenance if any. ★Always relay the included disclaimer and citation to the user★.

Input parameters:

- `slug` (string, required): system slug from renkeimap_find_system, e.g. "kintone"

### `renkeimap_brief` (~152 tokens)

システムを特定して稼働状況と対処をまとめて返す

One round trip = renkeimap_find_system + renkeimap_status + renkeimap_hintpack. Give either a slug or a free-text query (system name); returns the resolved system, its current externally-observed status (same shape as renkeimap_status) and the static hint pack (same shape as renkeimap_hintpack). Use this first in support conversations; fall back to the single tools when you need only one part. ★Always relay the included disclaimer and citation★.

Input parameters:

- `query` (string): system name as the user wrote it, used when slug is unknown
- `slug` (string): system slug, e.g. "kintone" (preferred when known)

### `renkeimap_status_history` (~206 tokens)

過去の障害とメンテナンスの記録を返す

Vendor-published incident history and announced maintenance for one system, as collected and verbatim-checked by IT連携マップ (the vendor's own records — not our observation). Returns, for the counted period: number of incidents, frequency per month, duration median/max (only for records where the vendor stated an end time — the count is given), common start weekdays and hours (JST), most-named components; the same numbers for announced maintenance; and the most recent records with the vendor's original title, an editorial Japanese translation for English titles, a short excerpt and the source URL. Read-only. Use when the user asks how often a system goes down, when its maintenance usually happens, or whether a past outage was reported. Systems without collected records return found:false.

Input parameters:

- `limit` (number): how many recent records to return (1-30, default 10)
- `slug` (string, required): system slug, e.g. "kintone"

### `renkeimap_hintpack` (~70 tokens)

エラー文の対処を返す

Static public knowledge for one system: what its vendor error messages mean, official support/contact URLs, login method shape. Sourced from public vendor pages (entries carry sources). No user data. Cite when used.

Input parameters:

- `slug` (string, required): system slug, e.g. "kintone"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jp-renkeimap-renkeimap-info/renkeimap#diagnostics

## Score history

- 2026-10-04: 76
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 75
- 2026-09-29: 75
- 2026-09-28: 74
- 2026-09-27: 74
- 2026-09-26: 73
- 2026-09-25: 73
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 71
- 2026-09-21: 71

## Common questions

### What is the jp.renkeimap/renkeimap-info MCP server?

jp.renkeimap/renkeimap-info is an MCP server listed in the public MCP registry as jp.renkeimap/renkeimap-info. 日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）. This page covers its hosted endpoint (https://renkeimap.jp/mcp).

### Is the jp.renkeimap/renkeimap-info MCP server safe to use?

jp.renkeimap/renkeimap-info scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the jp.renkeimap/renkeimap-info MCP server expose?

jp.renkeimap/renkeimap-info exposes 8 tools: renkeimap_find_system, renkeimap_system_facts, renkeimap_pair, renkeimap_compare, renkeimap_status, and 3 more. Their descriptions and schemas cost roughly 954 tokens of context every time the server is loaded.

### Does the jp.renkeimap/renkeimap-info MCP server require authentication?

No. We connected to jp.renkeimap/renkeimap-info without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the jp.renkeimap/renkeimap-info MCP server still maintained?

jp.renkeimap/renkeimap-info is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://renkeimap.jp/mcp
- Website: https://renkeimap.jp/guide/learn/our-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/jp-renkeimap-renkeimap-info/renkeimap.xml
- Changelog JSON feed: https://verifymcp.io/servers/jp-renkeimap-renkeimap-info/renkeimap.json
- HTML version of this page: https://verifymcp.io/servers/jp-renkeimap-renkeimap-info/renkeimap