mcp-registry/cn.mackorn/mackorn-cone-crusher · v0.2.2
As of 2026-10-27 01:33 UTC, the Mackorn Cone Crusher MCP server is up with a Glimind reliability score of 64/100 (grade C). Over the last 30 days it answered 97.5% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 7 minutes.
MACKORN hydraulic cone crusher selection and crushing-plant design. 21 tools, callable over HTTP.
Point your MCP client at this streamable-http endpoint: https://mackorn.cn/ai/api/mcp.php
29 of 29 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
Reachable 97.5% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~3,721 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 20 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcn.mackorn%2Fmackorn-cone-crusher/fixes
{
"name": "mackorn_capacity_check",
"description": "给定 MACKORN 机型 + 腔型 + 紧边排矿口 CSS，从《NH_NS系列技术参数大全》腔型×CSS 详表查出生产能力区间 t/h（无详表的机型按系列区间外推并标注为近似），同时返回排矿口范围合规性、最大给料限制、外形尺寸与重量 | mackorn_capacity_check",
"inputSchema": {
"type": "object",
"required": [
"model",
"css"
],
"properties": {
"css": {
"type": "number",
"description": "紧边排矿口 CSS，mm。"
},
"model": {
"enum": [
"NH200",
"NH300",
"NH400",
"NH600",
"NH700",
"NH860",
"NH865",
"NH890",
"NH895",
"NS200",
"NS300",
"NS400",
"NS600"
],
"type": "string",
"description": "机型型号。"
},
"cavity": {
"enum": [
"EC",
"C",
"MC",
"M",
"MF",
"F",
"EF",
"EFX",
"EEF"
],
"type": "string",
"description": "腔型代码。"
},
"target_tph": {
"type": "number",
"description": "目标产量 t/h（可选）。填了本工具会直接给出【能否达到】的判定 —— 复核既有设备时必填。"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "mackorn_cost_estimate",
"description": "MACKORN 液压圆锥破投资与运营成本估算：按机型与台数算装机功率、年电耗、年电费、吨电耗与吨电费 | mackorn_cost_estimate",
"inputSchema": {
"type": "object",
"required": [
"model"
],
"properties": {
"tph": {
"type": "number",
"description": "该机型对应处理量 t/h，用于吨成本换算。"
},
"model": {
"enum": [
"NH200",
"NH300",
"NH400",
"NH600",
"NH700",
"NH860",
"NH865",
"NH890",
"NH895",
"NS200",
"NS300",
"NS400",
"NS600"
],
"type": "string",
"description": "机型型号。"
},
"units": {
"type": "integer",
"default": 1,
"description": "台数（默认 1）。"
},
"term_years": {
"type": "integer",
"description": "融资租赁年限。"
},
"annual_rate": {
"type": "number",
"description": "融资租赁年利率（小数，如 0.06）；不填则不做月供测算。"
},
"load_factor": {
"type": "number",
"description": "负荷率 0-1。"
},
"hours_per_year": {
"type": "integer",
"description": "年运行小时数。"
},
"liner_life_hours": {
"type": "number",
"description": "衬板寿命 h（项目实测值，用于算衬板吨成本）。"
},
"electricity_price": {
"type": "number",
"description": "电价 元/kWh。"
},
"liner_cost_per_set": {
"type": "number",
"description": "单套衬板价格 元/套。"
},
"unit_price_wan_cny": {
"type": "number",
"description": "实际商务单价 万元/台（有则优先于参考区间）。"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "mackorn_knowledge_update",
"description": "把新采集到的行业情报/竞品动态/专利/标准/案例写入 MACKORN 持久化知识库，并自动完成：①来源可信度分级（1-5，白名单域名提档）②数值矛盾检测（功率/产能/CSS/价格/能耗等字段两两比对，超容差即记冲突）③版本演进判定（矛盾处置率≥0.8 且覆盖率 | mackorn_knowledge_update",
"inputSchema": {
"type": "object",
"required": [
"entries"
],
"properties": {
"actor": {
"type": "string",
"description": "操作者（如 销售-戴雷 / ai）。"
},
"entries": {
"type": "array",
"items": {
"type": "object",
"required": [
"title",
"content",
"source_url"
],
"properties": {
"kind": {
"enum": [
"intel",
"patent",
"standard",
"market",
"spec",
"price",
"case",
"correction"
],
"type": "string",
"description": "条目类型。"
},
"tags": {
"type": "array",
"items": {
"type": "string"
},
"description": "标签，如 [\"竞品\",\"山特维克\"]。"
},
"title": {
"type": "string",
"description": "标题（必填）。"
},
"content": {
"type": "string",
"description": "正文/事实与数字（必填）。"
},
"subject": {
"type": "string",
"description": "主题键：把\"讲同一件事\"的条目归到同一主题（如 \"300TPH-圆锥破配置\"），矛盾检测只在该主题内比较。型号类条目通常自带型号实体，可不填。"
},
"source_url": {
"type": "string",
"description": "来源链接或可核查出处（必填，缺失即拒收）。"
},
"source_type": {
"enum": [
"official",
"academic",
"report",
"conference",
"media",
"expert"
],
"type": "string",
"description": "来源类型，影响可信度基线。"
},
"publish_date": {
"type": "string",
"description": "发布日期 YYYY-MM-DD。"
},
"citation_count": {
"type": "integer",
"description": "被引次数（>50 可信度 +1）。"
},
"has_peer_review": {
"type": "boolean",
"description": "是否同行评审（可信度 +1）。"
},
"verification_status": {
"enum": [
"pending",
"verified",
"cross_validated",
"disputed"
],
"type": "string",
"description": "核验状态。"
}
},
"additionalProperties": false
},
"description": "要写入的知识条目数组。每条必须带 title、content、source_url。"
},
"rationale": {
"type": "string",
"description": "本轮采集/更新的目的说明。"
},
"tolerance": {
"type": "number",
"description": "数值矛盾容差（默认 0.1，即相差 10% 以上才算矛盾）。"
},
"check_fields": {
"type": "array",
"items": {
"type": "string"
},
"description": "要检测矛盾的字段（默认全部）。"
},
"crushing_leverage_score": {
"type": "number",
"description": "破碎效率杠杆得分 0-1（用于版本演进判定）。"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/cn.mackorn/mackorn-cone-crusher"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/cn.mackorn/mackorn-cone-crusher"}) over MCP.
mackorn_requirement_intake ~895 tokensmackorn_proposal ~690 tokensmackorn_distributor_eval ~647 tokensmackorn_market_intel ~522 tokensmackorn_knowledge_update ~515 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcn.mackorn%2Fmackorn-cone-crusher?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcn.mackorn%2Fmackorn-cone-crusher?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcn.mackorn%2Fmackorn-cone-crusher.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcn.mackorn%2Fmackorn-cone-crusher.svg :target: https://glimind.com/server/mcp-registry%2Fcn.mackorn%2Fmackorn-cone-crusher?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:815b528391d70b8d…, first seen 2026-10-25, included at leaf 63177 of 76,610. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable ml servers · most reliable data servers · most reliable knowledge servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 01:33 UTC, the Mackorn Cone Crusher MCP server is up with a Glimind reliability score of 64/100 (grade C). Over the last 30 days it answered 97.5% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 7 minutes.
Mackorn Cone Crusher MCP server advertises 29 tools, including mackorn_automation_design, mackorn_beneficiation_selection, mackorn_calibrate, mackorn_capacity_check, mackorn_cone_selection.
Point your MCP client at this streamable-http endpoint: https://mackorn.cn/ai/api/mcp.php
Glimind scanned all 29 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.