_ registry / mcp http-sse · checked 2h ago

jp-recall

https://jp-recall.plugrail.dev

Registry code: 4ff0d8e10ac03f76

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://jp-recall.plugrail.dev/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is jp-recall live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is jp-recall free to use?
Yes — the hub reached it with no key and no payment.
What tools does jp-recall have?
2 tools: get_recall_detail, search_recalls.
Is jp-recall safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.5%

90 days 98.1%· all time 98.1%

latency
1,439ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 258 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search japanese product recalls
  • get details of a recall
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_recall_detail reads unknown 2h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "management_number"
      ],
      "properties": {
        "management_number": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "number"
            }
          ],
          "description": "11桁の管理番号。例: \"00000035877\""
        }
      }
    }
    arguments 20 lines
  • search_recalls reads unknown 2h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "anyOf": [
            {
              "type": "number"
            },
            {
              "type": "string"
            }
          ],
          "description": "取得件数 1〜15(省略時は15)。例: 15"
        },
        "cursor": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "number"
            }
          ],
          "description": "前回応答の nextCursor(透過・省略可)。"
        },
        "keyword": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "number"
            }
          ],
          "description": "検索キーワード(30文字以内)。例: \"サーキュレーター\""
        },
        "category": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "number"
            }
          ],
          "description": "カテゴリ 0-13(0=すべて)。例: \"0\"。1-13 指定時は keyword 空でも可"
        },
        "posted_since": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "number"
            }
          ],
          "description": "掲載日の下限(YYYY-MM-DD・両端含む。省略=下限なし)。例: \"2026-09-01\""
        },
        "posted_until": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "number"
            }
          ],
          "description": "掲載日の上限(YYYY-MM-DD・両端含む。省略=上限なし)。例: \"2026-09-30\""
        }
      }
    }
    arguments 72 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4ff0d8e10ac03f76.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4ff0d8e10ac03f76/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4ff0d8e10ac03f76/badge.svg)](https://brick.blue/agent/4ff0d8e10ac03f76?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on plugrail.dev 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.