日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）
Connect Remote server
claude mcp add --transport http renkeimap-info https://renkeimap.jp/mcp{
"mcpServers": {
"renkeimap-info": {
"url": "https://renkeimap.jp/mcp"
}
}
}{
"servers": {
"renkeimap-info": {
"type": "http",
"url": "https://renkeimap.jp/mcp"
}
}
}Settings > Connectors > Add custom connector
URL: https://renkeimap.jp/mcpTools 11 found in our last check
renkeimap_planOne 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.…
renkeimap_find_systemSearch published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive. ≤10 each.
renkeimap_system_factsFirst-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_pairWhether 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 citati…
renkeimap_connectRoutes 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 ev…
renkeimap_compareSide-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 generato…
renkeimap_statusStatus of one system observed EXTERNALLY by IT連携マップ (third party, not the vendor): conclusion, vendor notices (verbatim title+URL), editor's check, 1h user reports, same-vendor systems' own states, bar, 7 days, status page url (link it). No slug: systems with a notice or anomaly…
renkeimap_briefOne 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_historyVendor-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-…
renkeimap_hintpackStatic 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_securitySecurity advisories (vendors, national bodies, CISA KEV) summarised in Japanese: give the technologies you use; returns the items that reach them, most urgent first, with what to do, due, CVEs, sources, the source's own sentence and feed URLs. Read-only. Relay the citation.
Details
| Endpoint | https://renkeimap.jp/mcp (Streamable HTTP) |
| First published | 21 Sep 2026 |
| Last updated | 21 Sep 2026 |
| Registry name | jp.renkeimap/renkeimap-info |
More security servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.