Renkeimap Info MCP Server

by renkeimap Your server? Claim it

answering

Renkeimap Info is answering right now. Last checked 4 min ago. It exposes 11 tools.

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

Uptime history 50 days of history · worst day 86%

50 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1387 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 17

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 October 2026. No other catalogue keeps this.

8 Nov a tool appeared renkeimap_security

23 Oct a tool description was rewritten renkeimap_status

23 Oct a tool changed the parameters it asks for renkeimap_status

16 Oct a tool description was rewritten renkeimap_find_system

16 Oct a tool changed the parameters it asks for renkeimap_find_system

10 Oct 5 tool descriptions were rewritten renkeimap_brief, renkeimap_compare, renkeimap_connect and 2 more

10 Oct 2 tools appeared renkeimap_connect, renkeimap_plan

10 Oct a tool changed the parameters it asks for2 times that day renkeimap_connect

3 Oct 2 tools appeared renkeimap_brief, renkeimap_status_history

3 Oct a tool description was rewritten renkeimap_status

and 1 more, back to 3 October 2026

Nothing serious here today

Today is the operative word: we check Renkeimap Info every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add renkeimap-info --transport http https://renkeimap.jp/mcp

Settings → Connectors → Add custom connector, then paste this address

https://renkeimap.jp/mcp

~/.codex/config.toml

[mcp_servers.renkeimap-info]
url = "https://renkeimap.jp/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

renkeimap

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

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.

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_pair). detail:"full" adds the procedure and evidence. Read-only; no keys or values.

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

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 instead of guessing. Cite the included citation line when used.

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 agent), write_rules, citation. Read-only. Ambiguous names return candidates.

renkeimap_security

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

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

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.

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 (出典: IT連携マップ + 調査日 + URL).

Endpoints

URL	Transport	State	Latency	Checked
https://renkeimap.jp/mcp	streamable-http	answering	984 ms	4 min ago

Alternatives to Renkeimap Info

same job, measured the same way

Hpo Api

by pipeworx-io

HPO API MCP.

330 installs/wk 51 tools answering

Renkeimap Info — questions

Answers built from our own checks of this server.

What can Renkeimap Info do?

It exposes 11 tools, read directly from the server on our last check. Among them: renkeimap_brief, renkeimap_compare, renkeimap_connect, renkeimap_find_system, renkeimap_hintpack, renkeimap_pair and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Renkeimap Info working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1387 ms. The bar chart above shows every period we have measured.

How do I connect Renkeimap Info?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Renkeimap Info need an API key?

No. Renkeimap Info completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Renkeimap Info?

It answers our handshake in 1387 ms on average, which is faster than 3% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.