renkeimap-info

endpoint

https://renkeimap.jp/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is renkeimap-info live?

Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.

Is renkeimap-info free to use?

Not measured yet.

What tools does renkeimap-info have?

10 tools: renkeimap_status, renkeimap_hintpack, renkeimap_plan, renkeimap_system_facts, renkeimap_pair, renkeimap_connect, renkeimap_brief, renkeimap_status_history, ….

Is renkeimap-info safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• renkeimap_status reads unknown never probed

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

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "system slug from renkeimap_find_system, e.g. \"kintone\""
      }
    }
  }

  arguments 9 lines copy
• renkeimap_hintpack reads unknown never probed

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "system slug, e.g. \"kintone\""
      }
    }
  }

  arguments 12 lines copy
• renkeimap_plan unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "required": [
      "from",
      "to"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "destination system — a name or a slug"
      },
      "from": {
        "type": "string",
        "description": "source system — the name as the user wrote it, or a slug"
      },
      "agent": {
        "type": "string",
        "description": "your CLI, e.g. \"claude-code\" — the answer then carries that CLI's add line"
      }
    }
  }

  arguments 21 lines copy
• renkeimap_system_facts reads unknown never probed

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

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "system slug from renkeimap_find_system, e.g. \"kintone\""
      }
    }
  }

  arguments 12 lines copy
• renkeimap_pair reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "a",
      "b"
    ],
    "properties": {
      "a": {
        "type": "string",
        "description": "first system slug"
      },
      "b": {
        "type": "string",
        "description": "second system slug"
      }
    }
  }

  arguments 17 lines copy
• renkeimap_connect unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "system slug (from renkeimap_find_system), or a suite id as renkeimap_pair returns it (a.slug / b.slug) — then the answer lists each public member"
      },
      "detail": {
        "enum": [
          "short",
          "full"
        ],
        "type": "string",
        "description": "short (default) or full — full adds the issuing procedure, minimal scope and evidence"
      }
    }
  }

  arguments 20 lines copy
• renkeimap_brief reads unknown never probed

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

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "system slug, e.g. \"kintone\" (preferred when known)"
      },
      "query": {
        "type": "string",
        "description": "system name as the user wrote it, used when slug is unknown"
      }
    }
  }

  arguments 13 lines copy
• renkeimap_status_history reads unknown never probed

  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.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "system slug, e.g. \"kintone\""
      },
      "limit": {
        "type": "number",
        "description": "how many recent records to return (1-30, default 10)"
      }
    }
  }

  arguments 16 lines copy
• renkeimap_find_system reads unknown never probed

  Search published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive. ≤10 each.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "required": [],
    "properties": {
      "has": {
        "enum": [
          "api",
          "mcp",
          "csv",
          "trial",
          "status_page",
          "no_training",
          "domestic_data"
        ],
        "type": "string"
      },
      "query": {
        "type": "string",
        "description": "\"kintone\"・\"会計\"・\"iPaaS\""
      }
    }
  }

  arguments 22 lines copy
• renkeimap_compare reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "slugs"
    ],
    "properties": {
      "slugs": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 5,
        "minItems": 2,
        "description": "system or tool slugs, e.g. [\"freee-kaikei\",\"moneyforward-cloud-kaikei\",\"yayoi\"]"
      }
    }
  }

  arguments 17 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.