jp.renkeimap/renkeimap-info

Tools

• renkeimap_brief

  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★.

  shallow
• renkeimap_compare

  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.

  shallow
• 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.

  shallow
• renkeimap_find_system

  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.

  shallow
• 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.

  shallow
• 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.

  shallow
• 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.

  shallow
• renkeimap_status

  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 12x5min state bar, and announced maintenance if any. ★Always relay the included disclaimer and citation to the user★.

  shallow
• renkeimap_status_history

  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.

  shallow
• 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).

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/0c8bce1b-f887-483a-bd41-b08897612c5c/badge.svg)](https://vouch.tools/servers/0c8bce1b-f887-483a-bd41-b08897612c5c)