制造业管理工具箱 · Manufacturing Management Toolkit MCP server
com.gddynb/xingdao-managegddynb.comstreamable-httpv1.0.1Scanned
制造业管理工具箱:TBP问题解决/品质管理/TPM设备保全/J成本改善/OEE计算/活力组织诊断。一句话出成品报告。
9 tools: 8 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
8 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.
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 制造业管理工具箱 · Manufacturing Management Toolkit MCP server can do
The 制造业管理工具箱 · Manufacturing Management Toolkit MCP server is published by gddynb.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (8 tools: tbp_problem_solving, quality_management, device_management, cost_improvement and 4 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 13, 2026, version 1.0.1.
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.
9 tools
Changes things 8Claude Code: ask
cost_improvement制造业成本改善与 J 成本论测算:由累计产量/累计成本数据算 J 成本、J 收益率,给出改善方向与敏感性分析。 Args: points: 累计点数据 JSON 字符串,至少 2 个点,格式 [[累计产量, 累计成本], ...], 例如 '[[0,0],[5,12000],[40,20000]]'。 profit: 单位利润(数字,可留空,例如 '8000…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 制造业成本改善与 J 成本论测算:由累计产量/累计成本数据算 J 成本、J 收益率,给出改善方向与敏感性分析。 Args: points: 累计点数据 JSON 字符串,至少 2 个点,格式 [[累计产量, 累计成本], ...], 例如 '[[0,0],[5,12000],[40,20000]]'。 profit: 单位利润(数字,可留空,例如 '8000')。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息;付款后带入此参数重试。 license_key: 买断/年费客户的授权码(有授权码则免付款)。与 payment_proof 填其一。
device_management设备管理全生命周期(TPM)系统:按设备清单生成保全方式选择、七维计划、点检标准、MTBF/OEE 指标与术语字典。 Args: devices: 设备清单 JSON 字符串,至少 1 台,每台须有 id 与 name。 例如 '[{"id":"EQ-01","name":"注塑机","model":"HT-160"}]'。 payment_proof: 支…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 设备管理全生命周期(TPM)系统:按设备清单生成保全方式选择、七维计划、点检标准、MTBF/OEE 指标与术语字典。 Args: devices: 设备清单 JSON 字符串,至少 1 台,每台须有 id 与 name。 例如 '[{"id":"EQ-01","name":"注塑机","model":"HT-160"}]'。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息;付款后带入此参数重试。 license_key: 买断/年费客户的授权码(有授权码则免付款)。与 payment_proof 填其一。
manager_development中基层管理者育成 · 梯队健康度诊断:按后备人才池与现任管理者数据,算后备覆盖率、代理试岗率、资格达成度、退出健康度与 GL 监督时间被侵占,输出梯队诊断报告 + HR 台账 CSV。 Args: positions: 关键管理岗位数(整数,如 "6")。 managers: 现任管理者 JSON 数组字符串(可留空)。每条形如 {"id":"M01","n…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 中基层管理者育成 · 梯队健康度诊断:按后备人才池与现任管理者数据,算后备覆盖率、代理试岗率、资格达成度、退出健康度与 GL 监督时间被侵占,输出梯队诊断报告 + HR 台账 CSV。 Args: positions: 关键管理岗位数(整数,如 "6")。 managers: 现任管理者 JSON 数组字符串(可留空)。每条形如 {"id":"M01","name":"张GL","level":"GL","eval_result":82,"eval_prev":78,"supervision_ratio":0.62}。 candidates: 后备人才 JSON 数组字符串(与 managers 至少给一个)。每条形如 {"id":"C01","name":"李四","target_level":"GL","months_in_pool":9, "courses_done":["TWI-JI","TWI-JM","TBP/A3","安全管理","基础管理"], "kaizen_themes":3,"acting_months":4,"acting_score":81,"experience_years":7}。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息;付款后带入此参数重试。 license_key: 买断/年费客户的授权码(有授权码则免付款)。与 payment_proof 填其一。
manufacturing_analytics制造业深度数据分析:对 OEE / SPC / 设备 / 库存 / 交期 / 成本 数据做多维度分析,输出结论与改善优先级。至少提供其中一项。 Args: oee: OEE 相关数据(JSON 字符串)。 spc: 过程能力(Cpk 等)数据(JSON 字符串)。 device: 设备故障/停机数据(JSON 字符串)。 inventory: 库存数据(JS…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 制造业深度数据分析:对 OEE / SPC / 设备 / 库存 / 交期 / 成本 数据做多维度分析,输出结论与改善优先级。至少提供其中一项。 Args: oee: OEE 相关数据(JSON 字符串)。 spc: 过程能力(Cpk 等)数据(JSON 字符串)。 device: 设备故障/停机数据(JSON 字符串)。 inventory: 库存数据(JSON 字符串)。 delivery: 交期/OTIF 数据(JSON 字符串)。 cost: 成本数据(JSON 字符串)。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息;付款后带入此参数重试。 license_key: 买断/年费客户的授权码(有授权码则免付款)。与 payment_proof 填其一。
quality_management品质管理全生命周期系统:按丰田源头品质方法生成企划→研发→生产准备→号试→量产六阶段全套品质文档(QFD、DFMEA、控制计划等)。 Args: company: 企业名称。 product_type: 产品类别,例如「注塑件」「电机」。 module: 只生成某一模块时填 Q1–Q12,全部生成填 ALL(默认)。 payment_proof: 支付宝支付…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 品质管理全生命周期系统:按丰田源头品质方法生成企划→研发→生产准备→号试→量产六阶段全套品质文档(QFD、DFMEA、控制计划等)。 Args: company: 企业名称。 product_type: 产品类别,例如「注塑件」「电机」。 module: 只生成某一模块时填 Q1–Q12,全部生成填 ALL(默认)。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息;付款后带入此参数重试。 license_key: 买断/年费客户的授权码(有授权码则免付款)。与 payment_proof 填其一。
safety_audit重点灾害发生源审核:对隐患/发生源台账做「六大类重点灾害」归类、A/B/C 风险分级、点检周期建议与硬件优先违规检出,输出审核报告 + 规范化台账 CSV(可直接进 EHS/CMMS)。 Args: sources: 发生源条目 JSON 数组字符串,至少 1 条(上限 300)。每条形如 {"id":"SR-001","equipment":"CNC-07…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 重点灾害发生源审核:对隐患/发生源台账做「六大类重点灾害」归类、A/B/C 风险分级、点检周期建议与硬件优先违规检出,输出审核报告 + 规范化台账 CSV(可直接进 EHS/CMMS)。 Args: sources: 发生源条目 JSON 数组字符串,至少 1 条(上限 300)。每条形如 {"id":"SR-001","equipment":"CNC-07","source":"主轴皮带轮防护罩", "phenomenon":"防护罩螺栓缺失,手可触及旋转皮带轮","protection":"固定式防护罩(无联锁)", "severity":"致命|重伤|轻伤|无伤害","frequency":"经常|偶尔|极少", "countermeasures":["设备对策:加装联锁防护罩"],"owner":"保全班"}。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息;付款后带入此参数重试。 license_key: 买断/年费客户的授权码(有授权码则免付款)。与 payment_proof 填其一。
tbp_problem_solvingTBP 问题解决教练:用丰田 8 步法 + 5Why 三层 + 8×4 管理矩阵分析一个管理/设备/品质问题,输出完整分析报告。 Args: problem: 问题描述。建议 15 字以上,写清「对象 + 现象 + 量化数据」, 例如「3 号注塑机频繁停机,每次 40 分钟」。 data: 问题相关的量化数据,例如「月停机 6 次共 4 小时」。 targe…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 TBP 问题解决教练:用丰田 8 步法 + 5Why 三层 + 8×4 管理矩阵分析一个管理/设备/品质问题,输出完整分析报告。 Args: problem: 问题描述。建议 15 字以上,写清「对象 + 现象 + 量化数据」, 例如「3 号注塑机频繁停机,每次 40 分钟」。 data: 问题相关的量化数据,例如「月停机 6 次共 4 小时」。 target: 改善目标,例如「月停机 ≤ 1 次」。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息;付款后带入此参数重试。 license_key: 买断/年费客户的授权码(有授权码则免付款)。与 payment_proof 填其一。
vital_organization活力组织诊断与建设方案:诊断组织活力、输出信任/希望/价值/挑战四维建设方案与落地清单。 Args: industry: 所属行业。 headcount: 员工人数。 pain: 当前最困扰的组织问题。 goal: 期望达成的目标。 trust/hope/value/challenge: 四维评分 0–5(可留空,未填按行业基准估算)。 payment_pr…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 活力组织诊断与建设方案:诊断组织活力、输出信任/希望/价值/挑战四维建设方案与落地清单。 Args: industry: 所属行业。 headcount: 员工人数。 pain: 当前最困扰的组织问题。 goal: 期望达成的目标。 trust/hope/value/challenge: 四维评分 0–5(可留空,未填按行业基准估算)。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息;付款后带入此参数重试。 license_key: 买断/年费客户的授权码(有授权码则免付款)。与 payment_proof 填其一。
Only reads 1Show 1 read-only tool
list_services列出本工具箱全部服务、价格与所需输入(下单前先看这个,或用于向用户报价)。No findings
Why it is in this group
- The name "list_services" says "list": a word for reading.
Description, as the server wrote it 列出本工具箱全部服务、价格与所需输入(下单前先看这个,或用于向用户报价)。
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 private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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.
Looked at Nov 20, 2026, 18:39 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: initialize answered HTTP 404.
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
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.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 8 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http xingdao-manage https://polyester-appease-bulldog.ngrok-free.dev/mcpclaude mcp add --transport http xingdao-manage https://polyester-appease-bulldog.ngrok-free.dev/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__xingdao-manage__list_services"
],
"ask": [
"mcp__xingdao-manage__tbp_problem_solving",
"mcp__xingdao-manage__quality_management",
"mcp__xingdao-manage__device_management",
"mcp__xingdao-manage__cost_improvement",
"mcp__xingdao-manage__vital_organization",
"mcp__xingdao-manage__manufacturing_analytics",
"mcp__xingdao-manage__safety_audit",
"mcp__xingdao-manage__manager_development"
],
"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 xingdao-manage. Review it before you use it.
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/com.gddynb/xingdao-manage/verify?hash=6ff9623059cbf13b49c52d9335a14d49ce816433b659ee81dda4abdbfd4630c9" | jq -e '.changed == false'Pinned hash 6ff9623059cb, from Nov 13, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.gddynb/xingdao-manage/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.gddynb/xingdao-manage)Source: MCP Registry. Synced Oct 21, 2026, 17:55 UTC.
制造业管理工具箱 · Manufacturing Management Toolkit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 8 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 制造业管理工具箱 · Manufacturing Management Toolkit MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the 制造业管理工具箱 · Manufacturing Management Toolkit 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 制造业管理工具箱 · Manufacturing Management Toolkit MCP server have?
- 9 tools: 8 write, 1 read. tbp_problem_solving, quality_management, device_management, cost_improvement, vital_organization, manufacturing_analytics, safety_audit, manager_development and 1 more.
Does the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.