jp.renkeimap/renkeimap-info

Est-ce que jp.renkeimap/renkeimap-info est sûr ?

Au dernier audit MCP Hub, le serveur MCP « jp.renkeimap/renkeimap-info » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 10 outils

• renkeimap_brief≈ 164 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · optionnel
    system slug, e.g. "kintone" (preferred when known)
  • query · string · optionnel
    system name as the user wrote it, used when slug is unknown

  Exemple d'appel

  {"name": "renkeimap_brief", "arguments": {"slug": "texte", "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_compare≈ 180 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • slugs · array · requis
    system or tool slugs, e.g. ["freee-kaikei","moneyforward-cloud-kaikei","yayoi"]

  Exemple d'appel

  {"name": "renkeimap_compare", "arguments": {"slugs": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_connect≈ 222 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    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 · string · optionnel · short | full
    short (default) or full — full adds the issuing procedure, minimal scope and evidence

  Exemple d'appel

  {"name": "renkeimap_connect", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_find_system≈ 137 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • has · string · optionnel · api | mcp | csv | trial | status_page | no_training | domestic_data
  • query · string · optionnel
    "kintone"・"会計"・"iPaaS"

  Exemple d'appel

  {"name": "renkeimap_find_system", "arguments": {"has": "api", "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_hintpack≈ 125 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    system slug, e.g. "kintone"

  Exemple d'appel

  {"name": "renkeimap_hintpack", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_pair≈ 158 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • a · string · requis
    first system slug
  • b · string · requis
    second system slug

  Exemple d'appel

  {"name": "renkeimap_pair", "arguments": {"a": "texte", "b": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_plan≈ 211 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • to · string · requis
    destination system — a name or a slug
  • from · string · requis
    source system — the name as the user wrote it, or a slug
  • agent · string · optionnel
    your CLI, e.g. "claude-code" — the answer then carries that CLI's add line

  Exemple d'appel

  {"name": "renkeimap_plan", "arguments": {"to": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_status≈ 155 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    system slug from renkeimap_find_system, e.g. "kintone"

  Exemple d'appel

  {"name": "renkeimap_status", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_status_history≈ 179 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    system slug, e.g. "kintone"
  • limit · number · optionnel
    how many recent records to return (1-30, default 10)

  Exemple d'appel

  {"name": "renkeimap_status_history", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renkeimap_system_facts≈ 145 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    system slug from renkeimap_find_system, e.g. "kintone"

  Exemple d'appel

  {"name": "renkeimap_system_facts", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://renkeimap.jp/mcp