jp.renkeimap由 renkeimap.jp 發布官方發布者v0.1.0更新於 Oct 24, 2026
日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）
唯讀 MCP，回傳附出處與調查日期的日本業務系統資訊：API、驗證、連接方式、比較與運作狀態。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/jp.renkeimap%2Frenkeimap-info/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"renkeimap-info": {
"type": "http",
"url": "https://renkeimap.jp/mcp"
}
}
}2 システムを繋いで移す案を 1 回で返す
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.
to必填from必填agentシステムを探す
Search published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive. ≤10 each.
hasquery1 システムの事実を返す
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).
slug必填2 システムが繋がるかを返す
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.
a必填b必填1 システムに繋ぐ道を安定な順に返す
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.
slug必填detail複数システムを横に並べて比べる
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.
slugs必填稼働状況を返す
Status 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 now. ★Relay disclaimer and citation★.
slugシステムを特定して稼働状況と対処をまとめて返す
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★.
slugquery過去の障害とメンテナンスの記録を返す
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.
slug必填limitエラー文の対処を返す
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.
slug必填已滿足適用檢查項的 83%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
請宣告包含 README 的 GitHub 儲存庫，或在 OAuth 受保護資源後設資料中提供 resource_documentation。
託管服務按其提供方的條款使用，因此這裡不要求授權條款。此檢查項不計入百分比。