# jp.renkeimap/renkeimap-info

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

- name: jp.renkeimap/renkeimap-info
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 69/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/jp.renkeimap%2Frenkeimap-info
- tools: https://api.protogrid.dev/v1/servers/jp.renkeimap%2Frenkeimap-info/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 97
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-94% +updated-30d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 69/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 10 of 10 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: renkeimap_plan (idempotentHint, openWorldHint); renkeimap_system_facts (idempotentHint, openWorldHint); renkeimap_connect (idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,403 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 11 tool changes in 30 days
- fail `stability.rug_pull`: 2 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 10, about 1,403 tokens to load them all
- tool set hash: 4a0841dc51512947be8ad082d8d8b589
- tools last changed: 2026-10-16T11:09:51.900Z
- badge: [![protogrid quality](https://protogrid.dev/badge/jp.renkeimap/renkeimap-info.svg)](https://protogrid.dev/servers/jp.renkeimap/renkeimap-info)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-16 `renkeimap_find_system` changed (description, inputSchema) **meaning changed**
  - before: 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.
  - after: Search published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive. ≤10 each.
- 2026-10-10 `renkeimap_status_history` changed (description) **meaning changed**
  - before: 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.
  - after: Vendor-published incident history and announced maintenance for one system, checked word for word (the vendor's own records, not our observation): counts, monthly frequency, durations (where the vendor gave an end), usual weekdays/hours (JST), recent records + source URLs. Read-only. found:false = not collected yet.
- 2026-10-10 `renkeimap_brief` changed (description)
  - before: 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★.
  - after: 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 tools. Use first in support conversations. ★Always relay the included disclaimer and citation★.
- 2026-10-10 `renkeimap_status` changed (description)
  - before: 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★.
  - after: Current status of one system as observed EXTERNALLY by IT連携マップ (third-party observation — NOT the vendor's official announcement): a closed-vocabulary conclusion, last-observed time, a 12-char state bar with legend, a 7-day hour table, announced maintenance. ★Always relay the included disclaimer and citation★.
- 2026-10-10 `renkeimap_compare` changed (description)
  - before: 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.
  - after: 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 = editorial tags + one-line lead + source URL + survey date; optional ◎○△× marks from a declared rule file. Same generator as /compare. No ranking, no score.
- 2026-10-10 `renkeimap_connect` changed (description, inputSchema)
  - before: How an agent can connect INTO one system, most stable route first: (1) the vendor's OFFICIAL MCP server — URL / auth / local command verbatim from the vendor's own text, with source and date (never a URL found by search); (2) the official API key or OAuth issuing procedure (who issues, which screen, minimal scope, token lifetime); (3) file (CSV) and screen routes (answered per pair by renkeimap_pair; screens by Leeda IN). Read-only; returns no keys or values.
  - after: 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 search); (2) official API key or OAuth issuing; (3) file/screen (renkeimap_pair). detail:"full" adds the procedure and evidence. Read-only; no keys or values.
- 2026-10-10 `renkeimap_plan` added
  - 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 one found by search — or API issuing), human steps, your CLI's add line (pass agent), write_rules, citation. Read-only. Ambiguous names return candidates.
- 2026-10-10 `renkeimap_connect` added
  - How an agent can connect INTO one system, most stable route first: (1) the vendor's OFFICIAL MCP server — URL / auth / local command verbatim from the vendor's own text, with source and date (never a URL found by search); (2) the official API key or OAuth issuing procedure (who issues, which screen, minimal scope, token lifetime); (3) file (CSV) and screen routes (answered per pair by renkeimap_pair; screens by Leeda IN). Read-only; returns no keys or values.
- 2026-10-03 `renkeimap_status_history` added
  - 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.
- 2026-10-03 `renkeimap_brief` added
  - 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★.

Full history: https://api.protogrid.dev/v1/servers/jp.renkeimap%2Frenkeimap-info/changes

## Remotes

- https://renkeimap.jp/mcp (streamable-http, auth none, reachable true, uptime30d 0.9369369)

## Packages

_none_

## 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 tools. Use first in support conversations. ★Always relay the included disclaimer and citation★.
- `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 = editorial tags + one-line lead + source URL + survey date; optional ◎○△× marks from a declared rule file. Same generator as /compare. No ranking, no score.
- `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 search); (2) official API key or OAuth issuing; (3) file/screen (renkeimap_pair). detail:"full" adds the procedure and evidence. Read-only; no keys or values.
- `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 (entries carry sources). No user data. Cite when used.
- `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-name overlap when available. Honest by design: an unmeasured pair says so instead of guessing. Cite the included citation line when used.
- `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 one found by search — or API issuing), human steps, your CLI's add line (pass agent), write_rules, citation. Read-only. Ambiguous names return candidates.
- `renkeimap_status`: Current status of one system as observed EXTERNALLY by IT連携マップ (third-party observation — NOT the vendor's official announcement): a closed-vocabulary conclusion, last-observed time, a 12-char state bar with legend, a 7-day hour table, announced maintenance. ★Always relay the included disclaimer and citation★.
- `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, monthly frequency, durations (where the vendor gave an end), usual weekdays/hours (JST), recent records + source URLs. Read-only. found:false = not collected yet.
- `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 response carries a citation line; when you use these facts in an answer, cite it (出典: IT連携マップ + 調査日 + URL).