Skip to content

renkeimap-info MCP server

jp.renkeimap/renkeimap-inforenkeimap.jpstreamable-httpv0.1.0Scanned

日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP(IT連携マップ)

11 tools: 1 do something that can't be undone, 6 change things and 4 only read.

Tools: 0 delete, 1 irreversible, 6 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the renkeimap-info MCP server can do

The renkeimap-info MCP server is published by renkeimap.jp, a domain the MCP Registry verified. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (renkeimap_plan) and create or change data (6 tools: renkeimap_system_facts, renkeimap_pair, renkeimap_connect, renkeimap_brief and 2 more), but cannot delete data. 4 tools only read.

1 tool reads private data (renkeimap_find_system); 2 tools bring in text other people can write (renkeimap_find_system and renkeimap_status); 1 tool can send data out of your system (renkeimap_plan). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Can't be undone 1Claude Code: ask
  • renkeimap_planOne 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 —…Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "renkeimap_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
Changes things 6Claude Code: ask
  • renkeimap_briefOne round trip = renkeimap_find_system + renkeimap_status + renkeimap_hintpack.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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★.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • renkeimap_connectRoutes 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • renkeimap_hintpackStatic public knowledge for one system: what its vendor error messages mean, official support/contact URLs, login method shape.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • renkeimap_pairWhether 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 av…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • renkeimap_securitySecurity advisories (vendors, national bodies, CISA KEV) in Japanese: technologies → the items that reach them, most urgent first, with what to do, due, CVEs, sources, the source's…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Security advisories (vendors, national bodies, CISA KEV) in Japanese: technologies → the items that reach them, most urgent first, with what to do, due, CVEs, sources, the source's own sentence, feed URLs; incidents_about → source-checked records of leaks / intrusions naming them. Read-only. Relay the citation.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • renkeimap_system_factsFirst-hand, survey-dated facts about one system (auth method, rate limits, CSV surfaces, pricing pages — tags + editorial summaries with sources).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
Only reads 4Show 4 read-only tools
  • renkeimap_compareSide-by-side comparison of 2-5 published systems/tools on the same ledger items (API, contract, price, rate limit, data location, exit, security…).No findings

    Why it is in this group

    • The name "renkeimap_compare" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • renkeimap_find_systemSearch published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "renkeimap_find_system" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "search" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Search published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive. ≤10 each.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • renkeimap_statusStatus 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 sys…Reads text others writeNo findings

    Why it is in this group

    • The name "renkeimap_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "status" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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★.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • renkeimap_status_historyVendor-published incident history and announced maintenance for one system, checked word for word (the vendor's own records, not our observation): counts, monthly frequency, durati…No findings

    Why it is in this group

    • The name "renkeimap_status_history" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__renkeimap-info__renkeimap_plan"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:15 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://renkeimap.jp/mcp: tools/list returned 11 tools to an anonymous client, including renkeimap_plan (irreversible), renkeimap_system_facts (write), renkeimap_pair (write), renkeimap_connect (write), renkeimap_brief (write) and 2 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 6 to 7

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "renkeimap_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added.+1 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
    • Tools that change things, listed without credentials: 6 to 7
  3. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__renkeimap-info__renkeimap_find_system",
      "mcp__renkeimap-info__renkeimap_compare",
      "mcp__renkeimap-info__renkeimap_status",
      "mcp__renkeimap-info__renkeimap_status_history"
    ],
    "ask": [
      "mcp__renkeimap-info__renkeimap_plan",
      "mcp__renkeimap-info__renkeimap_system_facts",
      "mcp__renkeimap-info__renkeimap_pair",
      "mcp__renkeimap-info__renkeimap_connect",
      "mcp__renkeimap-info__renkeimap_brief",
      "mcp__renkeimap-info__renkeimap_hintpack",
      "mcp__renkeimap-info__renkeimap_security"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as renkeimap-info. Review it before you use it.

Capability tags behind 3 rules
  • mcp__renkeimap-info__renkeimap_plan outbound
  • mcp__renkeimap-info__renkeimap_find_system private-data, untrusted-input
  • mcp__renkeimap-info__renkeimap_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/jp.renkeimap/renkeimap-info/verify?hash=d3527a85f7b434f2240bcd730664cedfe7360bd1128eca31fd54921189d86641" | jq -e '.changed == false'

Pinned hash d3527a85f7b4, from Nov 18, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/jp.renkeimap/renkeimap-info/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for jp.renkeimap/renkeimap-info
[![Anlyon Radar](https://radar.anlyon.com/badge/jp.renkeimap/renkeimap-info.svg)](https://radar.anlyon.com/servers/jp.renkeimap/renkeimap-info)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

renkeimap-info MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the renkeimap-info MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the renkeimap-info MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the renkeimap-info MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: renkeimap_plan.

What tools does the renkeimap-info MCP server have?

11 tools: 1 irreversible, 6 write, 4 read. renkeimap_plan, renkeimap_system_facts, renkeimap_pair, renkeimap_connect, renkeimap_brief, renkeimap_hintpack, renkeimap_security, renkeimap_find_system and 3 more.

Does the renkeimap-info MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the renkeimap-info MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): renkeimap_plan.

Has the renkeimap-info MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.