io.github.NorthWest999由 GitHub 帳號 NorthWest999 發布v1.0.0更新於 Oct 24, 2026
Is this product recalled in the EU? 46,506 official Safety Gate alerts by GTIN, brand or name.
遠端 MCP 伺服器，讓助理依條碼、品牌或名稱查詢歐盟 Safety Gate 產品召回，並檢視品牌的召回歷史。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.NorthWest999%2Feu-safety-gate-recalls/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"eu-safety-gate-product-recalls": {
"type": "http",
"url": "https://nlarqk54pr464oxhmozxd2sc6e0pkdrd.lambda-url.eu-central-1.on.aws/mcp"
}
}
}The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation
2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).
Registry Working Group:
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via MCP_REGISTRY_DATABASE_URL (see docker-compose.yml for a working example):
Available tags:
latest, v1.0.0, v1.1.0, etc.main (latest main branch build)main-<date>-<sha> (specific commit builds)To publish a server, we've built a simple CLI. You can use it with:
See the publisher guide for more details.
There are also a few more helpful commands for development. Run make help to learn more, or look in Makefile.
Publishing supports multiple authentication methods:
The registry validates namespace ownership when publishing. E.g. to publish...:
io.github.domdomegg/my-cool-mcp you must login to GitHub as domdomegg, or be in a GitHub Action on domdomegg's reposme.adamjones/my-cool-mcp you must prove ownership of adamjones.me via DNS or HTTP challengeCheck out community projects to explore notable registry-related work created by the community.
See the documentation for more details if your question has not been answered here!
來源：README.md，提交 d75e8b2
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.
gtinbrandproductGet 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.
brand必填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.
levellimitcountrycategory已滿足適用檢查項的 90%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
請在儲存庫或註冊中心條目中宣告授權條款。
# Start full development environmentmake dev-compose# Run latest stable releasedocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
# Run latest from main branch (continuous deployment)docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
# Run specific release versiondocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
# Run development build from main branchdocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d# Build the latest CLImake publisher
# Use it!./bin/mcp-publisher --help# Run lint, unit tests and integration testsmake check├── cmd/ # Application entry points│ └── publisher/ # Server publishing tool├── data/ # Seed data├── deploy/ # Deployment configuration (Pulumi)├── docs/ # Documentation├── internal/ # Private application code│ ├── api/ # HTTP handlers and routing│ ├── auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)│ ├── config/ # Configuration management│ ├── database/ # Data persistence (PostgreSQL)│ ├── service/ # Business logic│ ├── telemetry/ # Metrics and monitoring│ └── validators/ # Input validation├── pkg/ # Public packages│ ├── api/ # API types and structures│ │ └── v0/ # Version 0 API types│ └── model/ # Data models for server.json├── scripts/ # Development and testing scripts├── tests/ # Integration tests└── tools/ # CLI tools and utilities └── validate-*.sh # Schema validation tools