Skip to content
Back to search
100
MCP live MCP 2025-06-18 streamable-http

jp.renkeimap/renkeimap-info

jp.renkeimap/renkeimap-info

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

Watch this dependency Share evidence report
Uptime
100.0%
5 direct probes · 30d
Response
1106ms
last probe
Tools
11
callable
Resources
0
readable
Prompts
0
available
Score: 100/100
Handshake verified by our own probe.
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
11 tools, 0 resources, 0 prompts returned.
pass 3 or more catalogue items 10/10
11 items in total; 3 or more earns these points.
pass Describes itself 10/10
59 characters; more than 30 earns these points.

Tools · 11

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), hu…

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 …

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

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

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 …

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, ba…

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…

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

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

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, source…

How to use

Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://renkeimap.jp/mcp

Cursor or Cline: add to your MCP config:

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