INDIVIDUAL MCP TOOL

renkeimap_compare

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

renkeimap.jpnone authenticationAvailability not checked

LIVE ENDPOINT

https://renkeimap.jp/mcp

No auth detected

Connect to this endpoint to inspect the live schema for renkeimap_compare and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

renkeimap.jp

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: renkeimap-info
Remote MCP URL: https://renkeimap.jp/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

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

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

renkeimap_find_system — Search the published RenkeiMap ledger of Japanese business systems by name / vendor / category.
renkeimap_system_facts — First-hand, survey-dated facts about one system (auth method, rate limits, CSV surfaces, pricing pages — tags + editorial summaries with sources).
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.
renkeimap_status — Current operational status of one Japanese business system as observed EXTERNALLY by IT連携マップ (editorial third-party observation — NOT the vendor's official announcement).
renkeimap_hintpack — Static public knowledge for one system: what its vendor error messages mean, official support/contact URLs, login method shape.