Skip to content

PlugRail JP Recall MCP server

dev.plugrail/jp-recallplugrail.devstreamable-httpv0.1.0Scanned

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

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the PlugRail JP Recall MCP server can do

The PlugRail JP Recall MCP server is published by plugrail.dev, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools bring in text other people can write (search_recalls and get_recall_detail).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • get_recall_detail管理番号(11桁)からリコール詳細1件を取得します。入力例: {"management_number": "00000035877"}Reads text others writeNo findings

    Why it is in this group

    • The name "get_recall_detail" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    管理番号(11桁)からリコール詳細1件を取得します。入力例: {"management_number": "00000035877"}

    Annotations the server declares

    • title: リコール情報の詳細を取得
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • search_recalls消費者庁リコール情報サイトをキーワード+カテゴリで検索します。検索語は日本語推奨(英語の代表語は日本語に読み替えます。例: stroller→ベビーカー)。かな/全角/英語を読み替えて検索した場合は summary に「〜として検索しました」と明記します。JAN・型番の照会は keyword にそのまま渡せます。入力例: {"keyword": "サーキュレ…Reads text others writeNo findings

    Why it is in this group

    • The name "search_recalls" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    消費者庁リコール情報サイトをキーワード+カテゴリで検索します。検索語は日本語推奨(英語の代表語は日本語に読み替えます。例: 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件までを確認」と明記します。category は文字列 "0"〜"13"(数値の 0 は不可)。posted_since/posted_until は YYYY-MM-DD の実在日のみ(例: "2026-09-01"。2026/09/01・20260901 は不可)。

    Annotations the server declares

    • title: リコール情報を検索
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://jp-recall.plugrail.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.descope.com/v1/apps/agentic/P3JDYOMs4GLg0s3Zb26zp4RARA0j/RS3JDb1RbBrEmoZI7dxlb3esEhKVB
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jp-recall__search_recalls",
      "mcp__jp-recall__get_recall_detail"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jp-recall. Review it before you use it.

Capability tags behind 2 rules
  • mcp__jp-recall__search_recalls untrusted-input
  • mcp__jp-recall__get_recall_detail untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.plugrail/jp-recall/verify?hash=8715a368931af07da025cd497b1fa3c853982f5942f46c948f4f0461fe75a082" | jq -e '.changed == false'

Pinned hash 8715a368931a, from Nov 17, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.plugrail/jp-recall/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.plugrail/jp-recall
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.plugrail/jp-recall.svg)](https://radar.anlyon.com/servers/dev.plugrail/jp-recall)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.

PlugRail JP Recall MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PlugRail JP Recall MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the PlugRail JP Recall MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PlugRail JP Recall MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PlugRail JP Recall MCP server have?

2 tools: 2 read. search_recalls and get_recall_detail.

Does the PlugRail JP Recall MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PlugRail JP Recall MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the PlugRail JP Recall MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.