Connect PlugRail JP Recall and your agent gets 2 tools, among them get_recall_detail, search_recalls. It answers at https://jp-recall.plugrail.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 2 October 2026; the last check, on 16 November 2026, succeeded.
Search Japanese product recalls by keyword and category using public Consumer Affairs Agency data.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_recall_detail | 管理番号(11桁)からリコール詳細1件を取得します。入力例: {"management_number": "00000035877"} Inputs: management_number |
search_recalls | 消費者庁リコール情報サイトをキーワード+カテゴリで検索します。検索語は日本語推奨(英語の代表語は日本語に読み替えます。例: stroller→ベビーカー)。かな/全角/英語を読み替えて検索した場合は summary に「〜として検索しました」と明記します。JAN・型番の照会は keyword にそのまま渡せます。入力例: {"keyword": "サーキュレーター", "category": "0", "limit": 15}掲載日の絞り込み posted_since/pos Inputs: keyword, category, limit, cursor, posted_since, posted_until |
Every block below points at https://jp-recall.plugrail.dev/mcp. Pick your client and copy.
claude mcp add --transport http plugrail-jp-recall https://jp-recall.plugrail.dev/mcp
{
"mcpServers": {
"plugrail-jp-recall": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://jp-recall.plugrail.dev/mcp"]
}
}
}{
"mcpServers": {
"plugrail-jp-recall": {
"url": "https://jp-recall.plugrail.dev/mcp"
}
}
}{
"servers": {
"plugrail-jp-recall": {
"type": "http",
"url": "https://jp-recall.plugrail.dev/mcp"
}
}
}{
"context_servers": {
"plugrail-jp-recall": {
"url": "https://jp-recall.plugrail.dev/mcp"
}
}
}{
"mcpServers": {
"plugrail-jp-recall": {
"serverUrl": "https://jp-recall.plugrail.dev/mcp"
}
}
}{
"mcpServers": {
"plugrail-jp-recall": {
"url": "https://jp-recall.plugrail.dev/mcp"
}
}
}name: PlugRail JP Recall
version: 0.0.1
schema: v1
mcpServers:
- name: PlugRail JP Recall
type: streamable-http
url: https://jp-recall.plugrail.dev/mcp{
"mcpServers": {
"plugrail-jp-recall": {
"httpUrl": "https://jp-recall.plugrail.dev/mcp"
}
}
}{
"mcpServers": {
"plugrail-jp-recall": {
"type": "http",
"url": "https://jp-recall.plugrail.dev/mcp"
}
}
}{
"mcpServers": {
"plugrail-jp-recall": {
"url": "https://jp-recall.plugrail.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fjp-recall.plugrail.dev%2Fmcp&type=streamable_http&id=plugrail-jp-recall&name=PlugRail%20JP%20Recall
It answered our last check on 16 November 2026 in 904 ms. Over 4 checks since 2 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by plugrail.dev and served from jp-recall.plugrail.dev, the vendor's own domain: https://jp-recall.plugrail.dev/mcp.
2, as returned by the server's own tools/list on 19 November 2026: get_recall_detail, search_recalls.
It answered our last check on 16 November 2026 in 904 ms. Over 4 checks since 2 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://jp-recall.plugrail.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.plugrail. Endpoint host: jp-recall.plugrail.dev. ARD identifier: urn:air:dev.plugrail:mcp:jp-recall.
First indexed 2 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.