Renkeimap Info

jp.renkeimapPublished by renkeimap.jpOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Read-only MCP that returns sourced, survey-dated facts on Japanese business systems: APIs, auth, connection routes, comparisons and status.

What you can do
Search published systems, tools and guides by name, vendor, category or kind word, and read first-hand survey-dated facts about one system with citations. Check whether and how two systems can exchange data, and get routes into a system, official MCP server or API first. Compare two to five systems side by side on the same ledger items, and get a one-call brief combining search, status and hints. Read externally observed status, vendor incident history and maintenance, and static hints on error messages and support contacts.
When to use it
Useful when planning or supporting integrations between Japanese business systems, tools and iPaaS/RPA products, or when you need cited, dated facts on a vendor's API, auth method, pricing or outage status rather than guesses.
Requirements
Remote streamable HTTP endpoint; no package, environment variables or headers declared. No authentication is declared. Network access to the provider's endpoint is needed.
Before you install
Read-only tools that return third-party editorial content; responses carry citation and disclaimer lines that should be relayed when the facts are used. Status is observed externally by a third party, not by the vendor, and unmeasured pairs are reported as such. No credentials or user data are requested.

Installation

In SourceWeft

  1. Open Renkeimap Info in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/jp.renkeimap%2Frenkeimap-info/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "renkeimap-info": {
      "type": "http",
      "url": "https://renkeimap.jp/mcp"
    }
  }
}

Tools

10

renkeimap_plan

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.

Parameterstorequiredfromrequiredagent

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.

Parametershasquery

renkeimap_system_facts

1 システムの事実を返す

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

Parametersslugrequired

renkeimap_pair

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.

Parametersarequiredbrequired

renkeimap_connect

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.

Parametersslugrequireddetail

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 ranking, no score.

Parametersslugsrequired

renkeimap_status

稼働状況を返す

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

Parametersslug

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

Parametersslugquery

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 = not collected yet.

Parametersslugrequiredlimit

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.

Parametersslugrequired

Version history

1
  1. v0.1.0LatestSep 21, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.