_ registry / mcp streamable-http · checked 3h ago

eu-safety-gate-recalls

https://nlarqk54pr464oxhmozxd2sc6e0pkdrd.lambda-url.eu-central-1.on.aws

Registry code: 162d8080de6c0d6c

api record

Official EU Safety Gate (RAPEX) product-recall data. Use check_product_recall for a single product, get_brand_recall_history to assess a supplier, and list_recent_recalls to monitor new alerts. Source: © European Union, reused under Commission Decision 2011/833/EU.

endpoint
https://nlarqk54pr464oxhmozxd2sc6e0pkdrd.lambda-url.eu-central-1.on.aws/mcp
protocol
streamable-http ·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 eu-safety-gate-recalls live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is eu-safety-gate-recalls free to use?
Yes — the hub reached it with no key and no payment.
What tools does eu-safety-gate-recalls have?
3 tools: check_product_recall, list_recent_recalls, get_brand_recall_history.
Is eu-safety-gate-recalls 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
99.5%

90 days 99.1%· all time 99.1%

latency
97ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 531 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
security & compliance compliance & regulation
used for
  • check if a product was recalled in the eu
  • get brand recall history
  • list recent eu product recalls
takes → gives
text → data
tools
3 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

_ what it can do 3 tools
3 open 3 of 3 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.

  • check_product_recall reads open 6h ago

    Check whether a product has been recalled in the EU. Searches 46,506 official EU Safety Gate (RAPEX) alerts published since 2005 by GTIN/EAN barcode, brand and/or product name. Returns a verdict of "recalled", "possible_match" or "clear" with the matching official alerts. A "clear" verdict means no matching alert was found — it is not a safety certification.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "gtin": {
      "type": "string",
      "description": "EAN-8, UPC-A, EAN-13 or GTIN-14 barcode. The most reliable identifier."
    },
    "brand": {
      "type": "string",
      "description": "Brand or manufacturer name. German spelling variants are handled."
    },
    "product": {
      "type": "string",
      "description": "Product name or description."
    }
  }
}
    arguments 17 lines
  • list_recent_recalls reads open 6h ago

    List the most recent EU Safety Gate product recall alerts, optionally filtered by notifying country, product category or risk level. Updated daily, including official corrections and withdrawals.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "level": {
      "type": "string",
      "description": "Risk level, e.g. \"Serious risk\"."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "description": "How many alerts to return (1-50)."
    },
    "country": {
      "type": "string",
      "description": "Notifying country, e.g. \"Germany\", \"France\"."
    },
    "category": {
      "type": "string",
      "description": "Product category, e.g. \"Toys\", \"Cosmetics\"."
    }
  }
}
    arguments 22 lines
  • get_brand_recall_history reads open 6h ago

    Get the EU recall history of a brand: how many Safety Gate alerts it has on record, over what period, how many were classed as serious risk, the dominant hazard types, product categories and countries of origin. Useful for supplier and counterparty risk screening.

    mcp-tool

    {
  "type": "object",
  "required": [
    "brand"
  ],
  "properties": {
    "brand": {
      "type": "string",
      "description": "Brand or manufacturer name."
    }
  }
}
    arguments 12 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 162d8080de6c0d6c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/162d8080de6c0d6c/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/162d8080de6c0d6c/badge.svg)](https://brick.blue/agent/162d8080de6c0d6c?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
70%

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 on.aws 6 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.