IT連携マップ MCP server

• Registry namejp.renkeimap/renkeimap-infoverified in the MCP registry

The registry name sits under renkeimap.jp. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools10
• Server calls itselfrenkeimap-info
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 161 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer759 ms
• Space in an agent's context≈ 1,400 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsA · 98 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 1 of 10

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…

• 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 (出典…

• 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…

• 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_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…

• 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)…

• 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…

• 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…

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