Allergen Detector

io.github.daniellemeng1022由 GitHub 账号 daniellemeng1022 发布v0.1.0更新于 Oct 26, 2026

根据每位家庭成员的过敏情况检查食品和化妆品成分，包括隐藏名称。

AI 翻译由 AI 模型根据下方的原文描述翻译，可能有误。

原文描述

Checks food and cosmetic ingredients against each household member's allergies, incl. hidden names.

已验证Streamable HTTP可网页运行

概览

Allergen Detector 的托管 MCP 服务（allergen-detector-mcp.onrender.com）；可选 API 密钥；Streamable HTTP；3 个工具。

暂无 AI 概览：以下信息来自注册中心条目和服务本身。

端点
allergen-detector-mcp.onrender.com
最近检查

安装

在 SourceWeft 中

  1. 打开 控制台中的 Allergen Detector，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.daniellemeng1022%2Fallergen-detector/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "allergen-detector": {
      "type": "http",
      "url": "https://allergen-detector-mcp.onrender.com/mcp"
    }
  }
}

README

Allergen Detector MCP

The Allergen Detector matching engine as an MCP server, so AI assistants and shopping agents (ChatGPT, Claude, and others) can check a product against a household's allergies before recommending or buying it.

It uses the same matcher.js and allergen map as the Chrome extension (51 allergens, 1,078 names). The map refreshes daily from GitHub, so map updates reach agents with no redeploy.

Tools

ToolWhat it does
check_product_allergensChecks an ingredient list against one or more people's allergens (with severity) and returns who is affected, by which ingredient, and why. "Free from" claims never hide a real ingredient.
lookup_ingredientTells which allergen an ingredient name belongs to ("sodium caseinate" → milk).
list_supported_allergensLists the allergens the service covers.

The same checks are also a plain web API for agents that don't use MCP: POST /api/check, POST /api/lookup and GET /api/allergens, described at /openapi.json.

API keys are optional. Set API_KEYS="muse=<key>,acme=<key>" on the host to give each partner its own key, sent as X-API-Key or Authorization: Bearer. Requests without a key still work; a wrong key gets a 401. A valid key names the partner in /stats.

All tools are read-only and stateless. Nothing about the person (allergens, ingredients) is stored or logged. The only log is an anonymous count of tool calls per day, for measuring traction.

Run it

bash
npm installnpm test           # end-to-end test over MCPnpm start          # remote server: http://localhost:3000/mcpnpm run stdio      # local server for Claude Desktop and similarnpm run sync       # copy the latest matcher.js and map from the extension

To use it locally in Claude Desktop, add this to the mcpServers section of its config:

json
"allergen-detector": { "command": "node", "args": ["/path/to/allergen-mcp/server.js", "--stdio"] }

Launch steps

  1. Host it at a public HTTPS URL. Render or Fly.io can run npm start from a GitHub repo for $0–7/month. Later, point mcp.safi.ai at it.
  2. Privacy policy and terms page. Every directory requires one. Until safi.ai is live, host it on GitHub Pages. Its main point: no health data is stored.
  3. List it in the official MCP Registry (registry.modelcontextprotocol.io) with the mcp-publisher CLI, under io.github.daniellemeng1022/allergen-detector. Many clients and directories pull from it.
  4. Submit to the community directories: Smithery, Glama, PulseMCP and mcp.so.
  5. Claude: anyone can add it today as a custom connector by pasting the URL. To appear in Anthropic's connectors directory, submit it through their directory form.
  6. ChatGPT: test it in developer mode, then submit it as an app through OpenAI's Apps SDK submission process. This needs a verified developer account.
  7. Meta Muse (do this first): submit at muse.ai/platform. Choose "Existing MCP," enter the hosted URL, choose "API keys" and give Meta a key from API_KEYS (e.g. muse=…) so its calls show up as muse in /stats and payments to "no," then describe the service. Meta tests the live endpoint, so step 1 has to be done first. Muse already shops at Sephora, Walmart, Best Buy and the Shopify catalog, which covers both of our categories (cosmetics and food).
  8. Instinct and similar assistants: Instinct doesn't document custom MCP support. It shops through Shopify and Shop Pay. Reach out for a partnership instead.
  9. Shopping agents: contact teams building agentic-commerce products and offer the endpoint free during a pilot.
  10. Measure: set STATS_KEY on the host, then open https://<your-url>/stats?key=<STATS_KEY> to see calls by day, agent and tool. A connect count is an agent connecting; tool counts are real checks. /stats resets when the server restarts, but every count is also a [usage] JSON line in the host's logs. Track weekly checks and the number of distinct agents.

Before scaling

  • Add rate limiting and an API key for heavy business users. Keep a free tier.
  • Keep the disclaimer in every response. Don't present results as medical advice.

来源：README.md，提交 3963d31

工具

3

check_product_allergens

Check a product for allergens

Check a product's ingredient list against the allergies of one or more people in a household. Catches allergens listed under other names (e.g. "arachis oil" for peanut, "casein" for milk, Latin plant names in cosmetics) and does not let "free from" claims hide a real ingredient. Covers food and cosmetics. Call this before recommending or buying a food, cosmetic or household product for someone with allergies.

输入参数household必填ingredients必填product_name

lookup_ingredient

Look up an ingredient

Tell which allergens, if any, an ingredient name belongs to, e.g. "sodium caseinate" -> milk, "Prunus amygdalus dulcis oil" -> tree nuts, "DMDM hydantoin" -> formaldehyde releasers.

输入参数ingredient必填

list_supported_allergens

List supported allergens

List the allergens this service can check (food and cosmetic), with the other names users may type for them.

无需输入参数。

版本历史

1
  1. v0.1.0最新Oct 26, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。