Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

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

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

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "renkeimap-info": {
      "type": "remote",
      "url": "https://renkeimap.jp/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "renkeimap-info": {
      "type": "http",
      "url": "https://renkeimap.jp/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=renkeimap-info&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vcmVua2VpbWFwLmpwL21jcCJ9"
}

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

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

extensions:
  "renkeimap-info":
    enabled: true
    name: "renkeimap-info"
    type: streamable_http
    uri: "https://renkeimap.jp/mcp"
    timeout: 300

Quality 69 / 100needs work

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene86 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations10 of 10 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: renkeimap_plan (idempotentHint, openWorldHint); renkeimap_system_facts (idempotentHint, openWorldHint); renkeimap_connect (idempotentHint, openWorldHint); …
pass
tools.token_costabout 1,403 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability25 · weight 15

warn
stability.changes11 tool changes in 30 days
fail
stability.rug_pull2 tools kept their name but changed most of their description in 30 days; review before trusting them

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

10 tools, about 1,403 tokens to load them all · tool set 4a0841dc5151 · tools last changed 2026-10-16 · checked 2026-10-20 23:27 UTC

Tool changes

2026-10-16renkeimap_find_systemchangeddescription, input schemameaning changed
before
Search the published RenkeiMap ledger of Japanese business systems by name / vendor / category. Returns at most 10 candidates with their page URLs. Use renkeimap_system_facts for the facts of one system.
after · 19% of words in common
Search published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive. ≤10 each.
2026-10-10renkeimap_status_historychangeddescriptionmeaning changed
before
Vendor-published incident history and announced maintenance for one system, as collected and verbatim-checked by IT連携マップ (the vendor's own records — not our observation). Returns, for the counted period: number of incidents, frequency per month, duration median/max (only for records where the vendor stated an end time — the count is given), common start weekdays and hours (JST), most-named components; the same numbers for announced maintenance; and the most recent records with the vendor's original title, an editorial Japanese translation for English titles, a short excerpt and the source URL. Read-only. Use when the user asks how often a system goes down, when its maintenance usually happens, or whether a past outage was reported. Systems without collected records return found:false.
after · 32% of words in common
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.
2026-10-10renkeimap_briefchangeddescription
before
One round trip = renkeimap_find_system + renkeimap_status + renkeimap_hintpack. Give either a slug or a free-text query (system name); returns the resolved system, its current externally-observed status (same shape as renkeimap_status) and the static hint pack (same shape as renkeimap_hintpack). Use this first in support conversations; fall back to the single tools when you need only one part. ★Always relay the included disclaimer and citation★.
after · 52% of words in common
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★.
2026-10-10renkeimap_statuschangeddescription
before
Current operational status of one Japanese business system as observed EXTERNALLY by IT連携マップ (editorial third-party observation — NOT the vendor's official announcement). Returns a closed-vocabulary conclusion sentence, last-observed time, a 12-char state bar (one char per 5 min, legend included), a 7-day hour table, and announced maintenance if any. ★Always relay the included disclaimer and citation to the user★.
after · 75% of words in common
Current status of one system as observed EXTERNALLY by IT連携マップ (third-party observation — NOT the vendor's official announcement): a closed-vocabulary conclusion, last-observed time, a 12-char state bar with legend, a 7-day hour table, announced maintenance. ★Always relay the included disclaimer and citation★.
2026-10-10renkeimap_comparechangeddescription
before
Side-by-side comparison of 2-5 published systems/tools on the same ledger items (API availability, contract, price, rate limit, data location, exit, security…). Each cell = editorial tags + one-line lead + source URL + survey date; optional ◎○△× marks derived from tags by a declared rule file. Same generator as the /compare pages (single throat). No ranking, no score.
after · 90% of words in common
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.
2026-10-10renkeimap_connectchangeddescription, input schema
before
How an agent can connect INTO one system, most stable route first: (1) the vendor's OFFICIAL MCP server — URL / auth / local command verbatim from the vendor's own text, with source and date (never a URL found by search); (2) the official API key or OAuth issuing procedure (who issues, which screen, minimal scope, token lifetime); (3) file (CSV) and screen routes (answered per pair by renkeimap_pair; screens by Leeda IN). Read-only; returns no keys or values.
after · 63% of words in common
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.
2026-10-10renkeimap_planadded
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.
2026-10-10renkeimap_connectadded
How an agent can connect INTO one system, most stable route first: (1) the vendor's OFFICIAL MCP server — URL / auth / local command verbatim from the vendor's own text, with source and date (never a URL found by search); (2) the official API key or OAuth issuing procedure (who issues, which screen, minimal scope, token lifetime); (3) file (CSV) and screen routes (answered per pair by renkeimap_pair; screens by Leeda IN). Read-only; returns no keys or values.
2026-10-03renkeimap_status_historyadded
Vendor-published incident history and announced maintenance for one system, as collected and verbatim-checked by IT連携マップ (the vendor's own records — not our observation). Returns, for the counted period: number of incidents, frequency per month, duration median/max (only for records where the vendor stated an end time — the count is given), common start weekdays and hours (JST), most-named components; the same numbers for announced maintenance; and the most recent records with the vendor's original title, an editorial Japanese translation for English titles, a short excerpt and the source URL. Read-only. Use when the user asks how often a system goes down, when its maintenance usually happens, or whether a past outage was reported. Systems without collected records return found:false.
2026-10-03renkeimap_briefadded
One round trip = renkeimap_find_system + renkeimap_status + renkeimap_hintpack. Give either a slug or a free-text query (system name); returns the resolved system, its current externally-observed status (same shape as renkeimap_status) and the static hint pack (same shape as renkeimap_hintpack). Use this first in support conversations; fall back to the single tools when you need only one part. ★Always relay the included disclaimer and citation★.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 82 / 100

no-repository

provenance55

liveness97

freshness100

hygiene80

+dns-namespace +website +reachable +uptime-94% +updated-30d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://renkeimap.jp/mcp` streamable-http	none	yes	94%	832 ms	2025-06-18	2026-10-20

Tools (10)

`renkeimap_brief`read-only	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`read-only	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`read-only	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`read-only	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`read-only	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`read-only	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`read-only	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_status`read-only	Current status of one system as observed EXTERNALLY by IT連携マップ (third-party observation — NOT the vendor's official announcement): a closed-vocabulary conclusion, last-observed time, a 12-char state bar with legend, a 7-day hour table, announced maintenance. ★Always relay the included disclaimer and citation★.
`renkeimap_status_history`read-only	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`read-only	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).

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "jp.renkeimap/renkeimap-info",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://renkeimap.jp/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "websiteUrl": "https://renkeimap.jp/guide/learn/our-mcp-server",
  "description": "日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）"
}