Skip to content
Official MCP RegistryListed

jp.renkeimap/renkeimap-info

Part ofrenkeimap-infoMCP server

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

First seen 2 Oct 2026. Evidence as of 7 Oct 2026.

8
Tools
From an anonymous probe
1
Source listings
Each with its own history
3
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
renkeimap_briefOne 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★.Read-only
renkeimap_compareSide-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.Read-only
renkeimap_find_systemSearch 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.Read-only
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.Read-only
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 citation line when used.Read-only
renkeimap_statusCurrent 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★.Read-only
renkeimap_status_historyVendor-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.Read-only
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).Read-only

Change history

  1. renkeimap_status_history: tool added
  2. renkeimap_status: description changed (+"12-char" +"bar (one char per 5 min, legend included), a 7-day hour table," -"12x5min")
  3. renkeimap_brief: tool added
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryjp.renkeimap/renkeimap-info2 Oct 20267 Oct 20261
jp.renkeimap/renkeimap-info on Official MCP Registry | InvokeRank