# PlugRail JP Recall (remote · jp-recall.plugrail.dev)

Search Japanese product recalls by keyword and category using public Consumer Affairs Agency data.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `jp-recall.plugrail.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/dev-plugrail-jp-recall/jp-recall.md), [page](https://verifymcp.io/servers/dev-plugrail-jp-recall/jp-recall)

## Channel facts

- Endpoint: `https://jp-recall.plugrail.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-plugrail-jp-recall 'https://jp-recall.plugrail.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-plugrail-jp-recall": {
      "url": "https://jp-recall.plugrail.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-plugrail-jp-recall": {
      "type": "http",
      "url": "https://jp-recall.plugrail.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-plugrail-jp-recall]
url = "https://jp-recall.plugrail.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-plugrail-jp-recall": {
      "type": "remote",
      "url": "https://jp-recall.plugrail.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-plugrail-jp-recall --url 'https://jp-recall.plugrail.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-plugrail-jp-recall:
    url: "https://jp-recall.plugrail.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-plugrail-jp-recall": {
      "Transport": "http",
      "Url": "https://jp-recall.plugrail.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-plugrail-jp-recall -t streamable-http -u 'https://jp-recall.plugrail.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-plugrail-jp-recall": {
      "type": "http",
      "url": "https://jp-recall.plugrail.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 66, +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.

### 2026-10-14 (score 65, +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.

### 2026-10-12 (score 64, +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.

### 2026-10-10 (score 63, +1)

- [functional regression] Schema quality: 180 → 248

### 2026-10-04 (score 62, +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.

### 2026-10-03 (score 61, −1)

- [security] Tool “search_recalls” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “search_recalls” added an optional parameter “posted_since”
- [cosmetic] “search_recalls” added an optional parameter “posted_until”

### 2026-10-02 (score 62)

First indexed and scored.

## MCP tools (2)

### `search_recalls` (~434 tokens)

消費者庁リコール情報サイトをキーワード＋カテゴリで検索します。検索語は日本語推奨（英語の代表語は日本語に読み替えます。例: 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件までを確認」と明記します。

Input parameters:

- `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"

### `get_recall_detail` (~63 tokens)

管理番号（11桁）からリコール詳細1件を取得します。入力例: {"management_number": "00000035877"}

Input parameters:

- `management_number` (required): 11桁の管理番号。例: "00000035877"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-plugrail-jp-recall/jp-recall#diagnostics

## Score history

- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 65
- 2026-10-14: 65
- 2026-10-13: 64
- 2026-10-12: 64
- 2026-10-10: 63
- 2026-10-04: 62
- 2026-10-03: 61
- 2026-10-02: 62

## Common questions

### 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.

## Links

- Remote endpoint: https://jp-recall.plugrail.dev/mcp
- Repository: https://github.com/plugrail/servers
- Website: https://plugrail.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-plugrail-jp-recall/jp-recall.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-plugrail-jp-recall/jp-recall.json
- HTML version of this page: https://verifymcp.io/servers/dev-plugrail-jp-recall/jp-recall