jp.renkeimap/renkeimap-info
REMOTE · RENKEIMAP.JP · SCANNED OCT 4
日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 954 tokens (~119/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the jp.renkeimap/renkeimap-info MCP server?
jp.renkeimap/renkeimap-info is a hosted endpoint at https://renkeimap.jp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · renkeimap.jp
claude mcp add --transport http jp-renkeimap-renkeimap-info 'https://renkeimap.jp/mcp'
{
"mcpServers": {
"jp-renkeimap-renkeimap-info": {
"url": "https://renkeimap.jp/mcp"
}
}
} {
"servers": {
"jp-renkeimap-renkeimap-info": {
"type": "http",
"url": "https://renkeimap.jp/mcp"
}
}
} [mcp_servers.jp-renkeimap-renkeimap-info] url = "https://renkeimap.jp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-renkeimap-renkeimap-info": {
"type": "remote",
"url": "https://renkeimap.jp/mcp",
"enabled": true
}
}
} openclaw mcp add jp-renkeimap-renkeimap-info --url 'https://renkeimap.jp/mcp' --transport streamable-http
mcp_servers:
jp-renkeimap-renkeimap-info:
url: "https://renkeimap.jp/mcp" {
"McpServers": {
"jp-renkeimap-renkeimap-info": {
"Transport": "http",
"Url": "https://renkeimap.jp/mcp"
}
}
} assistant mcp add jp-renkeimap-renkeimap-info -t streamable-http -u 'https://renkeimap.jp/mcp'
{
"mcpServers": {
"jp-renkeimap-renkeimap-info": {
"type": "http",
"url": "https://renkeimap.jp/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 0
- Tool “renkeimap_status” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “renkeimap_brief” functional
- New tool “renkeimap_status_history” functional
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://renkeimap.jp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=renkeimap.jp | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6f81c87e5ce6420f0eb9e3ed1d8d6729 |
| SANs: renkeimap.jp, dev.renkeimap.jp, *.dev.renkeimap.jp | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of renkeimap.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| renkeimap.jp. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://renkeimap.jp/mcp | Verified | 200 | |
| http (plaintext) | http://renkeimap.jp/mcp | HTTPS enforced | 301 | https://renkeimap.jp/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
renkeimap_brief システムを特定して稼働状況と対処をまとめて返す ~152
One round trip = renkeimap_find_system + renkeimap_status + renkeimap_hintpack. Give either a slug or a free-text query (system name); returns the resolved system, its current externally-observed status (same shape as renkeimap_status) and the static hint pack (same shape as renkeimap_hintpack). Use this first in support conversations; fall back to the single tools when you need only one part. ★Always relay the included disclaimer and citation★.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | system name as the user wrote it, used when slug is unknown |
| slug | string | – | system slug, e.g. "kintone" (preferred when known) |
No output schema declared.
No examples provided.
renkeimap_compare 複数システムを横に並べて比べる ~126
Side-by-side comparison of 2-5 published systems/tools on the same ledger items (API availability, contract, price, rate limit, data location, exit, security…). Each cell = editorial tags + one-line lead + source URL + survey date; optional ◎○△× marks derived from tags by a declared rule file. Same generator as the /compare pages (single throat). No ranking, no score.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | system or tool slugs, e.g. ["freee-kaikei","moneyforward-cloud-kaikei","yayoi"] |
No output schema declared.
No examples provided.
renkeimap_find_system システムを探す ~89
Search the published RenkeiMap ledger of Japanese business systems by name / vendor / category. Returns at most 10 candidates with their page URLs. Use renkeimap_system_facts for the facts of one system.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | system or vendor name (Japanese or English), e.g. "kintone", "マネーフォワード", "会計" |
No output schema declared.
No examples provided.
renkeimap_hintpack エラー文の対処を返す ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | system slug, e.g. "kintone" |
No output schema declared.
No examples provided.
renkeimap_pair 2 システムが繋がるかを返す ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | first system slug |
| b | string | yes | second system slug |
No output schema declared.
No examples provided.
renkeimap_status 稼働状況を返す ~122
Current operational status of one Japanese business system as observed EXTERNALLY by IT連携マップ (editorial third-party observation — NOT the vendor's official announcement). Returns a closed-vocabulary conclusion sentence, last-observed time, a 12-char state bar (one char per 5 min, legend included), a 7-day hour table, and announced maintenance if any. ★Always relay the included disclaimer and citation to the user★.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | system slug from renkeimap_find_system, e.g. "kintone" |
No output schema declared.
No examples provided.
renkeimap_status_history 過去の障害とメンテナンスの記録を返す ~206
Vendor-published incident history and announced maintenance for one system, as collected and verbatim-checked by IT連携マップ (the vendor's own records — not our observation). Returns, for the counted period: number of incidents, frequency per month, duration median/max (only for records where the vendor stated an end time — the count is given), common start weekdays and hours (JST), most-named components; the same numbers for announced maintenance; and the most recent records with the vendor's original title, an editorial Japanese translation for English titles, a short excerpt and the source URL. Read-only. Use when the user asks how often a system goes down, when its maintenance usually happens, or whether a past outage was reported. Systems without collected records return found:false.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | how many recent records to return (1-30, default 10) |
| slug | string | yes | system slug, e.g. "kintone" |
No output schema declared.
No examples provided.
renkeimap_system_facts 1 システムの事実を返す ~100
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).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | system slug from renkeimap_find_system, e.g. "kintone" |
No output schema declared.
No examples provided.
What is the jp.renkeimap/renkeimap-info MCP server?
jp.renkeimap/renkeimap-info is an MCP server listed in the public MCP registry as jp.renkeimap/renkeimap-info. 日本の業務システムの API・認証・接続方式・稼働状況を、出典と調査日つきで返す読み取り専用 MCP（IT連携マップ）. This page covers its hosted endpoint (https://renkeimap.jp/mcp).
Is the jp.renkeimap/renkeimap-info MCP server safe to use?
jp.renkeimap/renkeimap-info scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the jp.renkeimap/renkeimap-info MCP server expose?
jp.renkeimap/renkeimap-info exposes 8 tools: renkeimap_find_system, renkeimap_system_facts, renkeimap_pair, renkeimap_compare, renkeimap_status, and 3 more. Their descriptions and schemas cost roughly 954 tokens of context every time the server is loaded.
Does the jp.renkeimap/renkeimap-info MCP server require authentication?
No. We connected to jp.renkeimap/renkeimap-info without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the jp.renkeimap/renkeimap-info MCP server still maintained?
jp.renkeimap/renkeimap-info is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.