Skip to content

BeaconMFG – China Supplier Directory MCP server

io.github.eiry16/beacon-mfg-mcpeiry16streamable-httpv1.12.13Scanned

China supplier directory MCP: search 210k+ firms by GB/T 4754 industry. Free, no install.

10 tools: 4 change things and 6 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • 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 BeaconMFG – China Supplier Directory MCP server can do

The BeaconMFG – China Supplier Directory MCP server is published by the GitHub account eiry16. It has 10 tools. It can create or change data (4 tools: suggest_filters, start_sourcing, answer_sourcing and refine_sourcing), but cannot delete data. 6 tools only read.

1 tool reads private data (get_vendor); 2 tools bring in text other people can write (get_vendor and get_onboarding_guide).

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 3 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.12.13.

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.

10 tools

Changes things 4Claude Code: ask
  • answer_sourcing续接 start_sourcing 的澄清轮次:把用户对澄清问题的回答写回,服务端据此**重新检索**(不是在旧结果里二次过滤 —— 过滤只能筛掉已有的,重检才能把更适合的捞上来)。 answers 的键用 clarifying_questions[].field(city / proc / cert),值为该问的 options[].value;此外可传 …No findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    续接 start_sourcing 的澄清轮次:把用户对澄清问题的回答写回,服务端据此**重新检索**(不是在旧结果里二次过滤 —— 过滤只能筛掉已有的,重检才能把更适合的捞上来)。 answers 的键用 clarifying_questions[].field(city / proc / cert),值为该问的 options[].value;此外可传 keyword 追加自由关键词。 回执里的 applied 是**已被采纳**的字段,ignored 是没被采纳的(多半是字段名写错)——看到 ignored 非空请对照 field 重发,不要以为已经生效。 轮次用完(2 轮)或问题已问清 → stage 变 shortlist,直接给初选名单。
  • refine_sourcing推荐轮交互。action 四选一: · best(默认)—— 按匹配度给前 3 家 + 每家一句「为什么是它」 · more —— 从本轮召回里再翻一批(value 给条数,默认 10)。不重复计费已给过的 · filter —— 追加一个约束重检(value 是要加的关键词,如「不锈钢」「ISO9001」) · details —— 看某一家在会话里的摘要…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    推荐轮交互。action 四选一: · best(默认)—— 按匹配度给前 3 家 + 每家一句「为什么是它」 · more —— 从本轮召回里再翻一批(value 给条数,默认 10)。不重复计费已给过的 · filter —— 追加一个约束重检(value 是要加的关键词,如「不锈钢」「ISO9001」) · details —— 看某一家在会话里的摘要(value 给 8 位 token)。**要完整档案/电话请调 get_vendor**:本工具只回会话里已有的字段,不额外取数。 ⚠ 名单只是初选:签约前的资质、产能、法人主体一律以 get_vendor / get_capability_card 的证据为准,不要把这里的排序当成「推荐这家」。
  • start_sourcing多轮寻源起手:把一句自然语言需求(「找东莞做注塑代工的,最好有 ISO9001」)变成一轮定向检索 + 1~2 个**只问必要信息**的澄清问题,返回 session_id 供 answer_sourcing / refine_sourcing 续接。 什么时候用它:用户有采购/代工/找厂意图,但需求还含糊(没说城市、没说工艺类别)——这种需求直接 sear…No findings

    Why it is in this group

    • The name "start_sourcing" says "start": a word for a change.
    Description, as the server wrote it
    多轮寻源起手:把一句自然语言需求(「找东莞做注塑代工的,最好有 ISO9001」)变成一轮定向检索 + 1~2 个**只问必要信息**的澄清问题,返回 session_id 供 answer_sourcing / refine_sourcing 续接。 什么时候用它:用户有采购/代工/找厂意图,但需求还含糊(没说城市、没说工艺类别)——这种需求直接 search_vendors 会拉回一堆跨行业噪声。 什么时候别用:需求一句话就能答(「东莞注塑厂有哪些」)→ 直接 search_vendors,省一次会话和一轮额度。 返回:stage(no_recall / clarifying / shortlist)、recalled(本轮取回家数)、clarifying_questions(每条带 field + options,**options 的取值直接来自候选集**,答了就能用来过滤)、preview(前 3 家)。 ⚠ 澄清问题最多 2 轮,且只问「答了能过滤」的字段(城市/工艺/认证)——交期、数量这类名录里没有的字段一律不问,问了也做不到。 ⚠ 会话 2 小时过期,且**只在同一出口 IP 下可取回**(纯 IP 身份,不认 API key);换网络/换代理后 session_id 会变成「不存在」。
  • suggest_filters把一句采购口语/用户原话拆成可执行的检索参数(拆词 + 别名 + 国标类名子串),给出候选检索词与候选 gb 码,并明确「名录未收录 ≠ 这家厂不存在」。 什么时候用:search_vendors 命中偏少/为 0、或你打算凭印象猜一个国标码时。典型链路:本工具拿候选 → search_vendors(gb=<code>) 验证 → get_vendor 取…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    把一句采购口语/用户原话拆成可执行的检索参数(拆词 + 别名 + 国标类名子串),给出候选检索词与候选 gb 码,并明确「名录未收录 ≠ 这家厂不存在」。 什么时候用:search_vendors 命中偏少/为 0、或你打算凭印象猜一个国标码时。典型链路:本工具拿候选 → search_vendors(gb=<code>) 验证 → get_vendor 取证。 ⚠ 远端**轻量版**:内嵌精简词表,不列全量货架、不给每类的完整条数;candidates 里的 gb 码是类名/别名推断的**低置信提示**,必须用 search_vendors 验证,不要直接拿它回答用户「属于某行业」。候选为空时按 next_calls 换词重试,别自己编 gb 码。 ⚠ 纯计算工具:不取企业记录,**不消耗记录额度**(但仍计入 IP 操作数)。
Only reads 6Show 6 read-only tools
  • get_capability_card取某家企业的能力卡(结构化工艺/设备/认证/产能证据,比 get_vendor 的档案更适合做「这家到底能不能做」的判断)。输入是 search_vendors 返回的 8 位 token。返回 found:false 表示这家暂无已发布的能力卡(不是错误)。No findings

    Why it is in this group

    • The name "get_capability_card" says "get": a word for reading.
    Description, as the server wrote it
    取某家企业的能力卡(结构化工艺/设备/认证/产能证据,比 get_vendor 的档案更适合做「这家到底能不能做」的判断)。输入是 search_vendors 返回的 8 位 token。返回 found:false 表示这家暂无已发布的能力卡(不是错误)。
  • get_entity_risk按 18 位统一社会信用代码取某法人主体的**政务事实卡**:税务、社保、司法、行政处罚、政府采购失信五类公开事实,压成 6 个法定资格核验项(三态 hit/clear/unknown)。用于政府采购资格审查、招商尽调、投标前自查。 ⚠ 输入是 **USCC**(营业执照上的 18 位代码),不是 search_vendors 的 8 位 token,也不是…No findings

    Why it is in this group

    • The name "get_entity_risk" says "get": a word for reading.
    Description, as the server wrote it
    按 18 位统一社会信用代码取某法人主体的**政务事实卡**:税务、社保、司法、行政处罚、政府采购失信五类公开事实,压成 6 个法定资格核验项(三态 hit/clear/unknown)。用于政府采购资格审查、招商尽调、投标前自查。 ⚠ 输入是 **USCC**(营业执照上的 18 位代码),不是 search_vendors 的 8 位 token,也不是企业名称 —— 本阶段不支持名称反查。 ⚠ `content[0].text` 是**已经排好版的事实卡**,请原样呈现给用户,不要重排表格、不要改小节顺序、不要把符号换成 emoji。需要精确取值时读 `structuredContent`。 ⚠ 任何 `actionable=false` 的核验项,**不得**表述为「无记录 / 无异常」,必须写明数据时点(`as_of`)并提示实时核验。 ⚠ `unknown` 是「没查过」,不是「没问题」;`hit` 只表示「有记录」,不表示「不合格」。本工具只给事实,不给结论、评分或建议 —— 结论由采购人依法自行判断。
  • get_onboarding_guide给供应商「入驻 / 认领」入口:返回可直接点开的控制台链接与步骤,外加一条**非手机 App** 的 HTTP/JSON 自助通道说明(供供应商自己的 Agent 认领并上传资料)。 当用户说「我是某某公司的」「我想入驻/上架产品/让客户搜到我」「我要认领我的企业」「怎么注册成供应商」「我的审核到哪一步了」时调用。 ⚠ 本工具**只给入口,绝不代办**:短信…Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    给供应商「入驻 / 认领」入口:返回可直接点开的控制台链接与步骤,外加一条**非手机 App** 的 HTTP/JSON 自助通道说明(供供应商自己的 Agent 认领并上传资料)。 当用户说「我是某某公司的」「我想入驻/上架产品/让客户搜到我」「我要认领我的企业」「怎么注册成供应商」「我的审核到哪一步了」时调用。 ⚠ 本工具**只给入口,绝不代办**:短信验证码与法人手机核验必须由用户在自己的浏览器里输入 —— 让他把验证码念给你,等于把「证明他是这家企业」的凭证交给第三方,还会进入对话上下文与日志。 ⚠ 不要替用户编造企业信息,不要承诺审核结果或时效,也不要把未认领的企业说成「已经属于你」。
  • get_vendor按主体 id 取完整中文档案。字段:company(名称)、address(地址)、lat/lng(坐标)、contact_phone(电话)、category(行业路径)、keywords(关键词)、region(省市区)、source/source_url(来源)、verified_at/last_verified_at(核验时间)。id 用 searc…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "contact": it reads contacts.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    按主体 id 取完整中文档案。字段:company(名称)、address(地址)、lat/lng(坐标)、contact_phone(电话)、category(行业路径)、keywords(关键词)、region(省市区)、source/source_url(来源)、verified_at/last_verified_at(核验时间)。id 用 search_vendors 返回的那个 8 位 token。若这家已归集到政府主体,回执里多一个 linked_entity:{uscc 统一社会信用代码, legal_name 法定登记名称, relation, origin, score}。`company` 是**经营招牌名**,`linked_entity.legal_name` 是**工商登记名**,两者经常不同;签约、开票、查资质一律用 legal_name + uscc。取多家请多次调用(每次一条计一次额度,重复看同一家不重复计)。
  • list_industries列出国标小类「货架」:只列名录里**已有企业**的类,附该类全库企业条数。用户原话跟任何类名都对不上字、或 suggest_filters 没给出可靠候选时,用它按语义自己挑码。 可传 keyword 按类名/码子串筛,parent 按门类字母(C)/大类(35)/中类(348)/小类(3484) 前缀缩小。挑 1~3 个 code 后调 search_ve…No findings

    Why it is in this group

    • The name "list_industries" says "list": a word for reading.
    Description, as the server wrote it
    列出国标小类「货架」:只列名录里**已有企业**的类,附该类全库企业条数。用户原话跟任何类名都对不上字、或 suggest_filters 没给出可靠候选时,用它按语义自己挑码。 可传 keyword 按类名/码子串筛,parent 按门类字母(C)/大类(35)/中类(348)/小类(3484) 前缀缩小。挑 1~3 个 code 后调 search_vendors(gb=<code>) 验证。 ⚠ 远端**轻量版**:内嵌精简货架,不含 5.9MB 完整 industry-index.json;industries[].records 是**全库该类企业总数**,不是本次匹配数,也不是本轮 city 范围内的条数。⚠ 纯计算工具:不取企业记录,**不消耗记录额度**(但仍计入 IP 操作数)。
  • search_vendors检索灯塔名录里的中国各行业经营主体(GB/T 4754 全门类,21 万家)。可按关键词(企业名/品牌/工艺/材料/认证/服务内容)、城市或区县、国标小类码过滤。返回精简档案,**字段名是短名**:id/token(8 位,传给 get_vendor 与 get_capability_card)、co(企业名称)、city(城市)、dist(区县)、gb(国…No findings

    Why it is in this group

    • The name "search_vendors" says "search": a word for reading.
    Description, as the server wrote it
    检索灯塔名录里的中国各行业经营主体(GB/T 4754 全门类,21 万家)。可按关键词(企业名/品牌/工艺/材料/认证/服务内容)、城市或区县、国标小类码过滤。返回精简档案,**字段名是短名**:id/token(8 位,传给 get_vendor 与 get_capability_card)、co(企业名称)、city(城市)、dist(区县)、gb(国标小类码)、proc(工艺)、mat(材料)、cert(认证)、has_phone(是否有电话)、tel(1=含电话,兼容旧客户端)、cap(能力键)、products(产品词)、lat/lng(坐标)。⚠ 检索结果**不含电话号码**:号码是一条一个额度的取证动作,请用 get_vendor(id);工艺证据档位在 pinf:省缺或 null=有事实工艺;A1~B0=零采集推断(分档非核实);class_default=挂的是国标小类默认工艺码,不是这家企业的事实工艺,严苛场景请降权。⚠ 关键词是**字面子串**匹配:口语词与归档写法不同会漏(「机加工」vs「机械零部件加工」)。0 命中时不要直接答「没有」—— 换同义词重试,或改用 city+gb 定向。 ⚠ 技术/能力词(「人工智能」「五轴加工」)在国标里可能根本没有对应小类;这种情况用 cap=<能力键>(suggest_filters 的 cap_candidates 会给)按能力索引定向,别硬塞进 query 做字面 AND,也别把 cap 当成 gb 码。

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 outbound.

Reads private data1
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, 18:21 UTC, unchanged since Nov 20, 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
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://beacon-mfg.pages.dev/mcp: tools/list returned 10 tools to an anonymous client, including suggest_filters (write), start_sourcing (write), answer_sourcing (write), refine_sourcing (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 0 to 4

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. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 4.View diff
    • Tools that change things, listed without credentials: 0 to 4
  2. Tools3 added, 1 changed.+3 added~1 changedView diff
  3. Tools1 added, 1 removed.+1 added−1 removedView diff
  4. Tools4 added.+4 addedView diff

Install

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

claude mcp add --transport http beacon-mfg https://beacon-mfg.pages.dev/mcp
claude mcp add --transport http beacon-mfg https://beacon-mfg.pages.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__beacon-mfg__search_vendors",
      "mcp__beacon-mfg__list_industries",
      "mcp__beacon-mfg__get_vendor",
      "mcp__beacon-mfg__get_capability_card",
      "mcp__beacon-mfg__get_onboarding_guide",
      "mcp__beacon-mfg__get_entity_risk"
    ],
    "ask": [
      "mcp__beacon-mfg__suggest_filters",
      "mcp__beacon-mfg__start_sourcing",
      "mcp__beacon-mfg__answer_sourcing",
      "mcp__beacon-mfg__refine_sourcing"
    ],
    "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 beacon-mfg. Review it before you use it.

Capability tags behind 2 rules
  • mcp__beacon-mfg__get_vendor private-data, untrusted-input
  • mcp__beacon-mfg__get_onboarding_guide 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/io.github.eiry16/beacon-mfg-mcp/verify?hash=6ae4cec3e1583120d1a8a602bbabf8faf0de76fda4473b8229fbd71410a984b4" | jq -e '.changed == false'

Pinned hash 6ae4cec3e158, from Nov 20, 2026, 04:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.eiry16/beacon-mfg-mcp/changes.xml

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

Badge

Anlyon Radar badge for io.github.eiry16/beacon-mfg-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.eiry16/beacon-mfg-mcp.svg)](https://radar.anlyon.com/servers/io.github.eiry16/beacon-mfg-mcp)

Source: MCP Registry · repository. Synced Nov 20, 2026, 04:17 UTC.

BeaconMFG – China Supplier Directory MCP server: questions and answers

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

Is the BeaconMFG – China Supplier Directory MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BeaconMFG – China Supplier Directory MCP server delete data?

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

Can the BeaconMFG – China Supplier Directory 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 BeaconMFG – China Supplier Directory MCP server have?

10 tools: 4 write, 6 read. suggest_filters, start_sourcing, answer_sourcing, refine_sourcing, search_vendors, list_industries, get_vendor, get_capability_card and 2 more.

Does the BeaconMFG – China Supplier Directory MCP server need sign-in or OAuth?

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

Does the BeaconMFG – China Supplier Directory MCP server send data to outside services?

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

Has the BeaconMFG – China Supplier Directory MCP server changed its tools?

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