jp. renkeimap/ renkeimap-info
by renkeimap.jp · remote · no sign-in to list tools · v0.1.0 · published by jp.renkeimap
日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP(IT連携マップ)
10 tools: 1 do something that can't be undone, 5 change things and 4 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone1Claude Code: ask: see these tools
- Changes things5Claude Code: ask: see these tools
- Only reads4Claude Code: allow: see these tools
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http renkeimap-info https://renkeimap.jp/mcpFindings
Matches of fixed checks, with the text they matched.
- Warnrenkeimap_plan
The server marks "renkeimap_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
10 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 —…1 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.
Findings
- Warn
The server marks "renkeimap_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
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 5Claude 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_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 4Claude Code: allow
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.No findings
Why it is in this group
- The name "renkeimap_find_system" says "find": a word for reading.
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_statusCurrent status of one system as observed EXTERNALLY by IT連携マップ (third-party observation — NOT the vendor's official announcement): a closed-vocabulary conclusion, last-observed tim…No findings
Why it is in this group
- The name "renkeimap_status" says "status": a word for reading.
Description, as the server wrote it 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★.
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.
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/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .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"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as renkeimap-info. Review it before you use it.