jp.renkeimap/renkeimap-info · v0.1.0 · data-and-databases
jp.renkeimap/renkeimap-info is healthy: it completed an MCP handshake in 2572 ms and exposes 10 tools.
日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）
Endpoint: https://renkeimap.jp/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 10 |
| Latency | 2572 ms |
| Last checked (UTC) | 2026-10-16T18:40:54.245Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T18:40:54.245Z | Healthy | 2572 | |
| 2026-10-15T12:20:21.323Z | Healthy | 3067 |
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 retur |
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_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). |
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_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 |
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 ran |
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 |
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_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 = n |
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. |