Home / MCP registry index / jp.renkeimap/renkeimap-info
jp.renkeimap/renkeimap-info
jp.renkeimap/renkeimap-info in the official MCP registry.
Endpoint https://renkeimap.jp/mcp.
The registry describes it as: 日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）
We read its 10 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
renkeimap_plan renkeimap_find_system renkeimap_system_facts renkeimap_pair renkeimap_connect renkeimap_compare renkeimap_status renkeimap_brief renkeimap_status_history renkeimap_hintpack
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/jp-renkeimap-renkeimap-info)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.