MCP servers › io.github.eiry16 › beacon-mfg-mcp
MCP server · registry snapshot 2026-11-14 · last tested 2026-11-14
beacon-mfg-mcp MCP server
Registry name io.github.eiry16/beacon-mfg-mcp
BeaconMFG – China Supplier Directory — the publisher's title
by eiry16 · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
China supplier directory MCP: search 210k+ firms by GB/T 4754 industry. Free, no install. — the publisher's description
Summary
io.github.eiry16/beacon-mfg-mcp is a remote and local MCP server listed in the official MCP registry at version 1.12.9, under the namespace of the GitHub account eiry16. Its linked repository, github.com/eiry16/beacon-mfg, belongs to the same GitHub account. On 2026-11-14 ProtocolProbe connected to it in read-only mode and read its inventory: 9 tools, 0 resources and 0 prompts.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #553 of 20,610 packages by monthly downloads
- Not ranked by stars: 2 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Package
- npm · listed version behind the latest release
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 9
- Last tested
- 2026-11-14
Tool list size
5,033 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (9 tools). Counted with Anthropic's token counter on 2026-11-14, from the tool list we read on 2026-11-14. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-14 (beacon-mfg.pages.dev), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.12.9).
Worth knowing before you connect it
- The registry lists 1.12.9; 1.12.10 is newer (1 release).
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-14
- Mode
- read-only (no tool calls)
- Latest version
- 1.12.9, published 2026-11-13 (registry, as of the 2026-11-14 snapshot)
- First listed version
- 2026-11-10 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 10 versions listed, 2026-11-10 to 2026-11-13; 10 in the 90 days before the 2026-11-14 snapshot.(versions still listed in the registry only)
Most recent 10 versions
1.12.9· 2026-11-131.12.8· 2026-11-131.12.7· 2026-11-131.12.6· 2026-11-131.12.5· 2026-11-131.12.4· 2026-11-131.12.3· 2026-11-121.12.2· 2026-11-111.12.1· 2026-11-101.12.0· 2026-11-10
- Registry data
- snapshot 2026-11-14
- Package and repository
- checked 2026-11-14
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 1.12.5 (published 2026-11-13) → 1.12.9 (published 2026-11-13), between the registry lists of 2026-11-13 and 2026-11-14.
The publisher published no GitHub release note for version 1.12.9: the repository has no release tagged for it.
Source: the official MCP Registry list on 2026-11-13 and on 2026-11-14; release notes from the GitHub Releases API, checked 2026-11-14.
What it is
What does this server offer?
Observed inventoryNone of its 9 tools are described as changing anything. For 9 the reading was uncertain, so no mark is shown.
- search_vendorson 11 other servers
“检索灯塔名录里的中国各行业经营主体(GB/T 4754 全门类,21 万家)。可按关键词(企业名/品牌/工艺/材料/认证/服务内容)、城市或区县、国标小类码过滤。返回精简档案,**字段名是短名**:id/token(8 位,传给 get_vendor 与 get_capability_card)、co(企业名称)、city(城市)、dist(区县)、gb(国标小类码)、proc(工艺)、mat(…”
8 inputs
querystring“关键词:企业名/品牌/工艺/材料/认证/服务内容子串。词表认得的品类词(兰花 / 医院 / 人工智能…)会自动带能力域加权,回执里有 cap_auto”citystring“城市名,如 深圳 / 东莞 / 苏州;也接受区县或县级市(昆山、海盐)。**省名不是合法取值**”gbstring“国标小类码,如 3484(机械零部件加工)、6210(正餐服务)。给了就只扫对应分片,召回与速度都更好”gbsarray“多个国标码一次定向(最多 6 个),比逐码调用省 RTT 与额度”capstring“能力键定向,如 tech_ai / cnc_turning;来自 suggest_filters 的 cap_candidates[].cap,**不是国标码**(最多 6 个用 caps)”capsarray“多个能力键一次定向(最多 6 个)”limitinteger“返回条数上限 1-200”offsetinteger“分页偏移”
- suggest_filterson 1 other server
“把一句采购口语/用户原话拆成可执行的检索参数(拆词 + 别名 + 国标类名子串),给出候选检索词与候选 gb 码,并明确「名录未收录 ≠ 这家厂不存在」。 什么时候用:search_vendors 命中偏少/为 0、或你打算凭印象猜一个国标码时。典型链路:本工具拿候选 → search_vendors(gb=<code>) 验证 → get_vendor 取证。 ⚠ 远端**轻量版**:内嵌精简…”
3 inputs, 1 required
querystringrequired“用户原话或检索词,如「找一下苏州做机加工的厂」”citystring“已知城市就直接给;不给则服务端从原话里认”limitinteger“候选 gb 码上限 1-20”
- list_industrieson 18 other servers
“列出国标小类「货架」:只列名录里**已有企业**的类,附该类全库企业条数。用户原话跟任何类名都对不上字、或 suggest_filters 没给出可靠候选时,用它按语义自己挑码。 可传 keyword 按类名/码子串筛,parent 按门类字母(C)/大类(35)/中类(348)/小类(3484) 前缀缩小。挑 1~3 个 code 后调 search_vendors(gb=<code>) 验证…”
4 inputs
keywordstring“可选,类名 / 国标码 / 门类路径的子串,如「酒」「014」「C」”parentstring“可选,门类字母(C) 或 大类(01)/中类(014)/小类(0141) 码前缀”limitinteger“返回条数 1-200”offsetinteger“分页偏移”
- get_vendoron 16 other servers
“按主体 id 取完整中文档案。字段:company(名称)、address(地址)、lat/lng(坐标)、contact_phone(电话)、category(行业路径)、keywords(关键词)、region(省市区)、source/source_url(来源)、verified_at/last_verified_at(核验时间)。id 用 search_vendors 返回的那个 8 位…”
1 input, 1 required
idstringrequired“8 位主体 token,来自 search_vendors 的 hits[].id”
- get_capability_card
“取某家企业的能力卡(结构化工艺/设备/认证/产能证据,比 get_vendor 的档案更适合做「这家到底能不能做」的判断)。输入是 search_vendors 返回的 8 位 token。返回 found:false 表示这家暂无已发布的能力卡(不是错误)。”
1 input, 1 required
idstringrequired“8 位主体 token,来自 search_vendors 的 hits[].id”
- start_sourcingon 1 other server
“多轮寻源起手:把一句自然语言需求(「找东莞做注塑代工的,最好有 ISO9001」)变成一轮定向检索 + 1~2 个**只问必要信息**的澄清问题,返回 session_id 供 answer_sourcing / refine_sourcing 续接。 什么时候用它:用户有采购/代工/找厂意图,但需求还含糊(没说城市、没说工艺类别)——这种需求直接 search_vendors 会拉回一堆跨行业…”
3 inputs, 1 required
demand_textstringrequired“一句话需求:品类/工艺/材料/地区/认证,越具体越好”citystring“已知城市就直接给,省掉一轮澄清”limitinteger“本轮取回家数 1-50(每家算 1 条额度)。默认 20,够做初步筛选”
- answer_sourcing
“续接 start_sourcing 的澄清轮次:把用户对澄清问题的回答写回,服务端据此**重新检索**(不是在旧结果里二次过滤 —— 过滤只能筛掉已有的,重检才能把更适合的捞上来)。 answers 的键用 clarifying_questions[].field(city / proc / cert),值为该问的 options[].value;此外可传 keyword 追加自由关键词。 回执…”
2 inputs, 1 required
session_idstringrequired“start_sourcing 返回的 session_id(必填)”answersobject“澄清回答,如 {"city":"东莞","proc":"injection_molding"};可加 keyword 追加自由关键词”
- refine_sourcing
“推荐轮交互。action 四选一: · best(默认)—— 按匹配度给前 3 家 + 每家一句「为什么是它」 · more —— 从本轮召回里再翻一批(value 给条数,默认 10)。不重复计费已给过的 · filter —— 追加一个约束重检(value 是要加的关键词,如「不锈钢」「ISO9001」) · details —— 看某一家在会话里的摘要(value 给 8 位 token)…”
3 inputs, 1 required
session_idstringrequired“会话 id(必填)”actionstring“交互类型,默认 best”valuestring“more 给条数 / filter 给关键词 / details 给 token”
- get_onboarding_guideon 2 other servers
“给供应商「入驻 / 认领」入口:返回可直接点开的控制台链接与步骤,外加一条**非手机 App** 的 HTTP/JSON 自助通道说明(供供应商自己的 Agent 认领并上传资料)。 当用户说「我是某某公司的」「我想入驻/上架产品/让客户搜到我」「我要认领我的企业」「怎么注册成供应商」「我的审核到哪一步了」时调用。 ⚠ 本工具**只给入口,绝不代办**:短信验证码与法人手机核验必须由用户在自己的…”
3 inputs
supplier_idstring“可选。已拿到的 8 位 token,用于生成直达深链”companystring“可选。企业名称,用于把步骤说得更具体”intentstring“claim=认领已收录企业(默认);register=库里没有要新建档;status=查审核进度;agent=看 Agent HTTP 自助通道契约”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-14.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 28
- Tools with a description
- 100% of 9
- Typical description length
- 383 characters
The tool set
Counted from the listing
- Tools
- 9
- Size of the list
- about 1,701 tokens for an agent to load (characters ÷ 4)
- Naming
- 9 of 9 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 9 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the npm package beacon-mfg-mcp
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"beacon-mfg-mcp": {
"command": "npx",
"args": [
"-y",
"beacon-mfg-mcp@1.12.9"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"beacon-mfg-mcp": {
"command": "npx",
"args": [
"-y",
"beacon-mfg-mcp@1.12.9"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"beacon-mfg-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"beacon-mfg-mcp@1.12.9"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"beacon-mfg-mcp","type":"stdio","command":"npx","args":["-y","beacon-mfg-mcp@1.12.9"]}'Claude Code
claude mcp add --transport stdio beacon-mfg-mcp -- npx -y beacon-mfg-mcp@1.12.9
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"beacon-mfg-mcp": {
"command": "npx",
"args": [
"-y",
"beacon-mfg-mcp@1.12.9"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"beacon-mfg-mcp": {
"command": "npx",
"args": [
"-y",
"beacon-mfg-mcp@1.12.9"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.beacon-mfg-mcp] command = "npx" args = ["-y", "beacon-mfg-mcp@1.12.9"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"beacon-mfg-mcp": {
"command": "npx",
"args": [
"-y",
"beacon-mfg-mcp@1.12.9"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y beacon-mfg-mcp@1.12.9
- Optional settings the entry also lists (left out above): BEACON_REPO.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-14 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://beacon-mfg.pages.dev/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"beacon-mfg-mcp": {
"url": "https://beacon-mfg.pages.dev/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"beacon-mfg-mcp": {
"type": "http",
"url": "https://beacon-mfg.pages.dev/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"beacon-mfg-mcp","type":"http","url":"https://beacon-mfg.pages.dev/mcp"}'Claude Code
claude mcp add --transport http beacon-mfg-mcp https://beacon-mfg.pages.dev/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"beacon-mfg-mcp": {
"type": "streamableHttp",
"url": "https://beacon-mfg.pages.dev/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"beacon-mfg-mcp": {
"httpUrl": "https://beacon-mfg.pages.dev/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.beacon-mfg-mcp] url = "https://beacon-mfg.pages.dev/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"beacon-mfg-mcp": {
"url": "https://beacon-mfg.pages.dev/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://beacon-mfg.pages.dev/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 1.12.9
- Latest stable
- 1.12.10
- Status
- behind the latest release (1 releases, 1 days)
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-14. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-14 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-znC1NqjlKu/Yx/hyo…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-11-14.
Usage
- Downloads
- 5,562 in the last month
Source: api.npmjs.org · 2026-11-14.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 1.12.9). Source: registry.npmjs.org/beacon-mfg-mcp/1.12.9 · read 2026-11-14.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/beacon-mfg-mcp/1.12.9 · read 2026-11-14.
- Node.js version (npm). Needs Node 16 or later (engines.node
>=16). Source: registry.npmjs.org/beacon-mfg-mcp/1.12.9 · read 2026-11-14. - MCP SDK in the package files. Ships no MCP SDK code in its own files by our rule, and does not list
@modelcontextprotocol/sdkor any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency. Source: registry.npmjs.org/beacon-mfg-mcp/-/beacon-mfg-mcp-1.12.9.tgz · read 2026-11-14. - Build workflow. No build provenance published for this version. Source: registry.npmjs.org/beacon-mfg-mcp/1.12.9 · read 2026-11-14.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-14.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-14. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-14. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-14. Source: read 2026-11-14.
- Cline marketplace. Not in the Cline marketplace on 2026-11-14. Source: read 2026-11-14.
Own host
- security.txt. https://beacon-mfg.pages.dev/.well-known/security.txt: the address answered HTTP 401 (2026-11-14). Source: beacon-mfg.pages.dev/.well-known/security.txt · read 2026-11-14.
- A2A agent card. https://beacon-mfg.pages.dev/.well-known/agent-card.json: the address answered HTTP 401 (2026-11-14). Source: beacon-mfg.pages.dev/.well-known/agent-card.json · read 2026-11-14.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint beacon-mfg.pages.dev/mcp | Session opened | matches | our test · 2026-11-14 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-14 |
| Version 1.12.9 on npm | Exists and can be installed | matches | npm · 2026-11-14 |
| Repository github.com/eiry16/beacon-mfg | Opens publicly | matches | api.github.com · 2026-11-14 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.eiry16
- GitHub owner
- a personal account (eiry16)
- Build record
- signed
- Repository
- github.com/eiry16/beacon-mfg
- Stars
- 2
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-14; security policy read from GitHub · 2026-11-12.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Tool list changes
Our reads compared · no tool calledHosted endpoint beacon-mfg.pages.dev/mcp
1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-13 to 2026-11-14; versions 1.12.5 to 1.12.9).
Last change seen between our reads on 2026-11-13 (version 1.12.5) and 2026-11-14 (version 1.12.9).
Added (3):
get_onboarding_guidelist_industriessuggest_filtersRemoved (1):
vendor_onboardingChanged (1):
search_vendors: description, input schemaCompared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-14 is not known yet. No tool was called. How it is compared
Choosing
Record checks
Public records · not a safety rating7 of 9 record checks met
- #553 of 20,610 packages by monthly downloads
- Not ranked by stars: 2 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists; a newer one is out.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-14 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.eiry16/beacon-mfg-mcp
Answered from the data aboveWho publishes io.github.eiry16/beacon-mfg-mcp?
The registry ties the namespace io.github.eiry16 to the GitHub account eiry16; only its owner can publish under it. Its linked repository, github.com/eiry16/beacon-mfg, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.eiry16/beacon-mfg-mcp safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.eiry16/beacon-mfg-mcp need an API key or sign-in?
It opened a session without any credential on 2026-11-14. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.eiry16/beacon-mfg-mcp been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Does io.github.eiry16/beacon-mfg-mcp publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
No. The registry lists 1.12.9; the latest stable release on npm is 1.12.10.
Where is the source code of io.github.eiry16/beacon-mfg-mcp?
In github.com/eiry16/beacon-mfg, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (no operator permission)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-14, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 367 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 9 tools, 0 resources, 0 prompts.
- 1,663 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.eiry16/beacon-mfg-mcp: MCP server record.” Data checked 2026-11-14. https://protocolprobe.com/mcp/servers/io.github.eiry16/beacon-mfg-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.eiry16/beacon-mfg-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology