# 制造业管理工具箱 · Manufacturing Management Toolkit (remote · polyester-appease-bulldog.ngrok-free.dev)

制造业管理工具箱：TBP问题解决/品质管理/TPM设备保全/J成本改善/OEE计算/活力组织诊断。一句话出成品报告。

- Trust score: 23/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `polyester-appease-bulldog.ngrok-free.dev`: 23/100 (this document), [markdown](https://verifymcp.io/servers/com-gddynb-xingdao-manage/polyester-appease-bulldog.md), [page](https://verifymcp.io/servers/com-gddynb-xingdao-manage/polyester-appease-bulldog)

## Channel facts

- Endpoint: `https://polyester-appease-bulldog.ngrok-free.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

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

### Claude

```bash
claude mcp add --transport http com-gddynb-xingdao-manage 'https://polyester-appease-bulldog.ngrok-free.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-gddynb-xingdao-manage": {
      "url": "https://polyester-appease-bulldog.ngrok-free.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gddynb-xingdao-manage": {
      "type": "http",
      "url": "https://polyester-appease-bulldog.ngrok-free.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-gddynb-xingdao-manage]
url = "https://polyester-appease-bulldog.ngrok-free.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gddynb-xingdao-manage": {
      "type": "remote",
      "url": "https://polyester-appease-bulldog.ngrok-free.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gddynb-xingdao-manage --url 'https://polyester-appease-bulldog.ngrok-free.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-gddynb-xingdao-manage:
    url: "https://polyester-appease-bulldog.ngrok-free.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-gddynb-xingdao-manage": {
      "Transport": "http",
      "Url": "https://polyester-appease-bulldog.ngrok-free.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gddynb-xingdao-manage -t streamable-http -u 'https://polyester-appease-bulldog.ngrok-free.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-gddynb-xingdao-manage": {
      "type": "http",
      "url": "https://polyester-appease-bulldog.ngrok-free.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 23, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 23, −49)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.87 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-03 (score 72, +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.

### 2026-11-02 (score 71, +48)

- [security improvement] Injection markers: unverified → pass
- [security improvement] 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.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.83
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-30 (score 23, −46)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.70 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-28 (score 69, +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.

### 2026-10-26 (score 68, +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.

### 2026-10-24 (score 67, +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.

## MCP tools (9)

### `tbp_problem_solving` (~254 tokens)

TBP 问题解决教练：用丰田 8 步法 + 5Why 三层 + 8×4 管理矩阵分析一个管理/设备/品质问题，输出完整分析报告。

    Args:
        problem: 问题描述。建议 15 字以上，写清「对象 + 现象 + 量化数据」，
                 例如「3 号注塑机频繁停机，每次 40 分钟」。
        data: 问题相关的量化数据，例如「月停机 6 次共 4 小时」。
        target: 改善目标，例如「月停机 ≤ 1 次」。
        payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。
        license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。

Input parameters:

- `data` (string)
- `license_key` (string)
- `payment_proof` (string)
- `problem` (string, required)
- `target` (string)

Output parameters:

- `result` (string)

### `quality_management` (~203 tokens)

品质管理全生命周期系统：按丰田源头品质方法生成企划→研发→生产准备→号试→量产六阶段全套品质文档（QFD、DFMEA、控制计划等）。

    Args:
        company: 企业名称。
        product_type: 产品类别，例如「注塑件」「电机」。
        module: 只生成某一模块时填 Q1–Q12，全部生成填 ALL（默认）。
        payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。
        license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。

Input parameters:

- `company` (string)
- `license_key` (string)
- `module` (string)
- `payment_proof` (string)
- `product_type` (string)

Output parameters:

- `result` (string)

### `device_management` (~186 tokens)

设备管理全生命周期（TPM）系统：按设备清单生成保全方式选择、七维计划、点检标准、MTBF/OEE 指标与术语字典。

    Args:
        devices: 设备清单 JSON 字符串，至少 1 台，每台须有 id 与 name。
                 例如 '[{"id":"EQ-01","name":"注塑机","model":"HT-160"}]'。
        payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。
        license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。

Input parameters:

- `devices` (string, required)
- `license_key` (string)
- `payment_proof` (string)

Output parameters:

- `result` (string)

### `cost_improvement` (~216 tokens)

制造业成本改善与 J 成本论测算：由累计产量/累计成本数据算 J 成本、J 收益率，给出改善方向与敏感性分析。

    Args:
        points: 累计点数据 JSON 字符串，至少 2 个点，格式 [[累计产量, 累计成本], ...]，
                例如 '[[0,0],[5,12000],[40,20000]]'。
        profit: 单位利润（数字，可留空，例如 '8000'）。
        payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。
        license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。

Input parameters:

- `license_key` (string)
- `payment_proof` (string)
- `points` (string, required)
- `profit` (string)

Output parameters:

- `result` (string)

### `vital_organization` (~248 tokens)

活力组织诊断与建设方案：诊断组织活力、输出信任/希望/价值/挑战四维建设方案与落地清单。

    Args:
        industry: 所属行业。
        headcount: 员工人数。
        pain: 当前最困扰的组织问题。
        goal: 期望达成的目标。
        trust/hope/value/challenge: 四维评分 0–5（可留空，未填按行业基准估算）。
        payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。
        license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。

Input parameters:

- `challenge` (string)
- `goal` (string)
- `headcount` (string)
- `hope` (string)
- `industry` (string)
- `license_key` (string)
- `pain` (string)
- `payment_proof` (string)
- `trust` (string)
- `value` (string)

Output parameters:

- `result` (string)

### `manufacturing_analytics` (~275 tokens)

制造业深度数据分析：对 OEE / SPC / 设备 / 库存 / 交期 / 成本 数据做多维度分析，输出结论与改善优先级。至少提供其中一项。

    Args:
        oee: OEE 相关数据（JSON 字符串）。
        spc: 过程能力（Cpk 等）数据（JSON 字符串）。
        device: 设备故障/停机数据（JSON 字符串）。
        inventory: 库存数据（JSON 字符串）。
        delivery: 交期/OTIF 数据（JSON 字符串）。
        cost: 成本数据（JSON 字符串）。
        payment_proof: 支付宝支付凭证。首次调用留空 → 返回付款信息；付款后带入此参数重试。
        license_key: 买断/年费客户的授权码（有授权码则免付款）。与 payment_proof 填其一。

Input parameters:

- `cost` (string)
- `delivery` (string)
- `device` (string)
- `inventory` (string)
- `license_key` (string)
- `oee` (string)
- `payment_proof` (string)
- `spc` (string)

Output parameters:

- `result` (string)

### `safety_audit` (~315 tokens)

重点灾害发生源审核：对隐患/发生源台账做「六大类重点灾害」归类、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 填其一。

Input parameters:

- `license_key` (string)
- `payment_proof` (string)
- `sources` (string, required)

Output parameters:

- `result` (string)

### `manager_development` (~349 tokens)

中基层管理者育成 · 梯队健康度诊断：按后备人才池与现任管理者数据，算后备覆盖率、代理试岗率、资格达成度、退出健康度与 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 填其一。

Input parameters:

- `candidates` (string)
- `license_key` (string)
- `managers` (string)
- `payment_proof` (string)
- `positions` (string)

Output parameters:

- `result` (string)

### `list_services` (~36 tokens)

列出本工具箱全部服务、价格与所需输入（下单前先看这个，或用于向用户报价）。

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-gddynb-xingdao-manage/polyester-appease-bulldog#diagnostics

## Score history

- 2026-11-06: 23
- 2026-11-05: 23
- 2026-11-04: 23
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 23
- 2026-10-31: 23
- 2026-10-30: 23
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 66
- 2026-10-22: 66
- 2026-10-21: 65
- 2026-10-20: 65
- 2026-10-19: 65
- 2026-10-18: 64
- 2026-10-17: 23
- 2026-10-16: 23
- 2026-10-15: 63
- 2026-10-14: 23
- 2026-10-13: 62
- 2026-10-12: 61
- 2026-10-10: 60
- 2026-10-08: 60

## Common questions

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

## Links

- Remote endpoint: https://polyester-appease-bulldog.ngrok-free.dev/mcp
- Website: https://gddynb.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-gddynb-xingdao-manage/polyester-appease-bulldog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gddynb-xingdao-manage/polyester-appease-bulldog/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-gddynb-xingdao-manage/polyester-appease-bulldog.json
- HTML version of this page: https://verifymcp.io/servers/com-gddynb-xingdao-manage/polyester-appease-bulldog