PlugRail JP Recall
REMOTE · JP-RECALL.PLUGRAIL.DEV
Search Japanese product recalls by keyword and category using public Consumer Affairs Agency data.
Available components
Last scanned (1 hour ago)
Scores higher than 56% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Search and Retrieval
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 497 tokens (~248/item across 2 items; 2 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 Management53
- Stability observed for 16 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Schema quality: 180 → 248 ▼ functional
- 4 Oct 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.
- 3 Oct 26 −1
- Tool “search_recalls” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “search_recalls” added an optional parameter “posted_since” cosmetic
- “search_recalls” added an optional parameter “posted_until” cosmetic
- 2 Oct 26 62
First indexed and scored.
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 18 Oct 2026 · Probed https://jp-recall.plugrail.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=plugrail.dev | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | da461e26835e38200e1060e3bbf53591 |
| SANs: plugrail.dev, jp-recall.plugrail.dev, *.jp-recall.plugrail.dev | ||||||
| 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 jp-recall.plugrail.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| plugrail.dev. | 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://jp-recall.plugrail.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jp-recall.plugrail.dev/mcp | Inconclusive | 405 |
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 →
get_recall_detail ~63
管理番号（11桁）からリコール詳細1件を取得します。入力例: {"management_number": "00000035877"}
| Name | Type | Req | Description |
|---|---|---|---|
| management_number | – | yes | 11桁の管理番号。例: "00000035877" |
No output schema declared.
No examples provided.
search_recalls ~434
消費者庁リコール情報サイトをキーワード＋カテゴリで検索します。検索語は日本語推奨（英語の代表語は日本語に読み替えます。例: stroller→ベビーカー）。かな/全角/英語を読み替えて検索した場合は summary に「〜として検索しました」と明記します。JAN・型番の照会は keyword にそのまま渡せます。入力例: {"keyword": "サーキュレーター", "category": "0", "limit": 15}掲載日の絞り込み posted_since/posted_until（YYYY-MM-DD・両端含む）を指定すると、上流の新しい順に最大5ページ（75件）まで走査して絞り込みます。total_count・range・nextCursor はいずれも limit 単位の論理位置（絞り込みありは絞り込み後、なしは上流順の続き）を示します。上限で打ち切った場合は summary に「上流の先頭75件までを確認」と明記します。
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | カテゴリ 0-13（0=すべて）。例: "0"。1-13 指定時は keyword 空でも可 |
| cursor | – | – | 前回応答の nextCursor（透過・省略可）。 |
| keyword | – | – | 検索キーワード（30文字以内）。例: "サーキュレーター" |
| limit | – | – | 取得件数 1〜15（省略時は15）。例: 15 |
| posted_since | – | – | 掲載日の下限（YYYY-MM-DD・両端含む。省略＝下限なし）。例: "2026-09-01" |
| posted_until | – | – | 掲載日の上限（YYYY-MM-DD・両端含む。省略＝上限なし）。例: "2026-09-30" |
No output schema declared.
No examples provided.
How do I install the PlugRail JP Recall MCP server?
PlugRail JP Recall is a hosted endpoint at https://jp-recall.plugrail.dev/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 · jp-recall.plugrail.dev
claude mcp add --transport http dev-plugrail-jp-recall 'https://jp-recall.plugrail.dev/mcp'
What is the PlugRail JP Recall MCP server?
PlugRail JP Recall is an MCP server listed in the public MCP registry as dev.plugrail/jp-recall. Search Japanese product recalls by keyword and category using public Consumer Affairs Agency data. This page covers its hosted endpoint (https://jp-recall.plugrail.dev/mcp).
Is the PlugRail JP Recall MCP server safe to use?
PlugRail JP Recall scores 66 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 PlugRail JP Recall MCP server expose?
PlugRail JP Recall exposes 2 tools: search_recalls, get_recall_detail. Their descriptions and schemas cost roughly 497 tokens of context every time the server is loaded.
Does the PlugRail JP Recall MCP server require authentication?
No. We connected to PlugRail JP Recall without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PlugRail JP Recall MCP server still maintained?
PlugRail JP Recall is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.