制造业管理工具箱 · Manufacturing Management Toolkit
REMOTE · POLYESTER-APPEASE-BULLDOG.NGROK-FREE.DEV
制造业管理工具箱：TBP问题解决/品质管理/TPM设备保全/J成本改善/OEE计算/活力组织诊断。一句话出成品报告。
Available components
Last scanned (1 hour ago)
Scores higher than 8% of remote servers
Reachable. Last reached 6 Nov 2026.
Category CI/CD and DevOps
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +48
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.83 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 30 Oct 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.70 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://polyester-appease-bulldog.ngrok-free.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.ngrok-free.dev | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5a41afeaafbd267d543db00f6d9469106fe |
| SANs: *.ngrok-free.dev, ngrok-free.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of polyester-appease-bulldog.ngrok-free.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| ngrok-free.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://polyester-appease-bulldog.ngrok-free.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://polyester-appease-bulldog.ngrok-free.dev/mcp | HTTPS enforced | 307 | https://polyester-appease-bulldog.ngrok-free.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cost_improvement ~216
制造业成本改善与 J 成本论测算：由累计产量/累计成本数据算 J 成本、J 收益率，给出改善方向与敏感性分析。 Args: points: 累计点数据 JSON 字符串，至少 2 个点，格式 [[累计产量, 累计成本], ...]， 例如 '[[0,0],[5,12000],[40,20000]]'。 profit: 单位利润（数字，可留空，例如 '8000'）。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。 license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。
| Name | Type | Req | Description |
|---|---|---|---|
| license_key | string | – | – |
| payment_proof | string | – | – |
| points | string | yes | – |
| profit | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
device_management ~186
设备管理全生命周期（TPM）系统：按设备清单生成保全方式选择、七维计划、点检标准、MTBF/OEE 指标与术语字典。 Args: devices: 设备清单 JSON 字符串，至少 1 台，每台须有 id 与 name。 例如 '[{"id":"EQ-01","name":"注塑机","model":"HT-160"}]'。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。 license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。
| Name | Type | Req | Description |
|---|---|---|---|
| devices | string | yes | – |
| license_key | string | – | – |
| payment_proof | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_services ~36
列出本工具箱全部服务、价格与所需输入（下单前先看这个，或用于向用户报价）。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
manager_development ~349
中基层管理者育成 · 梯队健康度诊断：按后备人才池与现任管理者数据，算后备覆盖率、代理试岗率、资格达成度、退出健康度与 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 填其一。
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | string | – | – |
| license_key | string | – | – |
| managers | string | – | – |
| payment_proof | string | – | – |
| positions | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
manufacturing_analytics ~275
制造业深度数据分析：对 OEE / SPC / 设备 / 库存 / 交期 / 成本 数据做多维度分析，输出结论与改善优先级。至少提供其中一项。 Args: oee: OEE 相关数据（JSON 字符串）。 spc: 过程能力（Cpk 等）数据（JSON 字符串）。 device: 设备故障/停机数据（JSON 字符串）。 inventory: 库存数据（JSON 字符串）。 delivery: 交期/OTIF 数据（JSON 字符串）。 cost: 成本数据（JSON 字符串）。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。 license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。
| Name | Type | Req | Description |
|---|---|---|---|
| cost | string | – | – |
| delivery | string | – | – |
| device | string | – | – |
| inventory | string | – | – |
| license_key | string | – | – |
| oee | string | – | – |
| payment_proof | string | – | – |
| spc | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
quality_management ~203
品质管理全生命周期系统：按丰田源头品质方法生成企划→研发→生产准备→号试→量产六阶段全套品质文档（QFD、DFMEA、控制计划等）。 Args: company: 企业名称。 product_type: 产品类别，例如「注塑件」「电机」。 module: 只生成某一模块时填 Q1–Q12，全部生成填 ALL（默认）。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。 license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| license_key | string | – | – |
| module | string | – | – |
| payment_proof | string | – | – |
| product_type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
safety_audit ~315
重点灾害发生源审核：对隐患/发生源台账做「六大类重点灾害」归类、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 填其一。
| Name | Type | Req | Description |
|---|---|---|---|
| license_key | string | – | – |
| payment_proof | string | – | – |
| sources | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tbp_problem_solving ~254
TBP 问题解决教练：用丰田 8 步法 + 5Why 三层 + 8×4 管理矩阵分析一个管理/设备/品质问题，输出完整分析报告。 Args: problem: 问题描述。建议 15 字以上，写清「对象 + 现象 + 量化数据」， 例如「3 号注塑机频繁停机，每次 40 分钟」。 data: 问题相关的量化数据，例如「月停机 6 次共 4 小时」。 target: 改善目标，例如「月停机 ≤ 1 次」。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。 license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | – |
| license_key | string | – | – |
| payment_proof | string | – | – |
| problem | string | yes | – |
| target | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
vital_organization ~248
活力组织诊断与建设方案：诊断组织活力、输出信任/希望/价值/挑战四维建设方案与落地清单。 Args: industry: 所属行业。 headcount: 员工人数。 pain: 当前最困扰的组织问题。 goal: 期望达成的目标。 trust/hope/value/challenge: 四维评分 0–5（可留空，未填按行业基准估算）。 payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。 license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。
| Name | Type | Req | Description |
|---|---|---|---|
| challenge | string | – | – |
| goal | string | – | – |
| headcount | string | – | – |
| hope | string | – | – |
| industry | string | – | – |
| license_key | string | – | – |
| pain | string | – | – |
| payment_proof | string | – | – |
| trust | string | – | – |
| value | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server?
制造业管理工具箱 · Manufacturing Management Toolkit is a hosted endpoint at https://polyester-appease-bulldog.ngrok-free.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · polyester-appease-bulldog.ngrok-free.dev
claude mcp add --transport http com-gddynb-xingdao-manage 'https://polyester-appease-bulldog.ngrok-free.dev/mcp'
What is the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server?
制造业管理工具箱 · Manufacturing Management Toolkit is an MCP server listed in the public MCP registry as com.gddynb/xingdao-manage. 制造业管理工具箱：TBP问题解决/品质管理/TPM设备保全/J成本改善/OEE计算/活力组织诊断。一句话出成品报告。 This page covers its hosted endpoint (https://polyester-appease-bulldog.ngrok-free.dev/mcp).
Is the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server safe to use?
制造业管理工具箱 · Manufacturing Management Toolkit scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server expose?
制造业管理工具箱 · Manufacturing Management Toolkit exposes 9 tools: tbp_problem_solving, quality_management, device_management, cost_improvement, vital_organization, and 4 more. Their descriptions and schemas cost roughly 2,082 tokens of context every time the server is loaded.
Does the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server require authentication?
Its publisher declares no required credentials for 制造业管理工具箱 · Manufacturing Management Toolkit. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server still maintained?
制造业管理工具箱 · Manufacturing Management Toolkit is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the 制造业管理工具箱 · Manufacturing Management Toolkit MCP server?
VerifyMCP ran 5 checks on 制造业管理工具箱 · Manufacturing Management Toolkit, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about 制造业管理工具箱 · Manufacturing Management Toolkit: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.