RoboParts 机器人零部件兼容性
REMOTE · ROBOPARTS.CC · SCANNED SEP 25
688 humanoid robot component entities with 4-dimension compatibility checking. Vendor-neutral.
Available components
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 fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2996 tokens (~272/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the RoboParts 机器人零部件兼容性 MCP server?
RoboParts 机器人零部件兼容性 is a hosted endpoint at https://roboparts.cc/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 · roboparts.cc
claude mcp add --transport http cc-roboparts-roboparts 'https://roboparts.cc/mcp'
{
"mcpServers": {
"cc-roboparts-roboparts": {
"url": "https://roboparts.cc/mcp"
}
}
} {
"servers": {
"cc-roboparts-roboparts": {
"type": "http",
"url": "https://roboparts.cc/mcp"
}
}
} [mcp_servers.cc-roboparts-roboparts] url = "https://roboparts.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cc-roboparts-roboparts": {
"type": "remote",
"url": "https://roboparts.cc/mcp",
"enabled": true
}
}
} openclaw mcp add cc-roboparts-roboparts --url 'https://roboparts.cc/mcp' --transport streamable-http
mcp_servers:
cc-roboparts-roboparts:
url: "https://roboparts.cc/mcp" {
"McpServers": {
"cc-roboparts-roboparts": {
"Transport": "http",
"Url": "https://roboparts.cc/mcp"
}
}
} assistant mcp add cc-roboparts-roboparts -t streamable-http -u 'https://roboparts.cc/mcp'
{
"mcpServers": {
"cc-roboparts-roboparts": {
"type": "http",
"url": "https://roboparts.cc/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 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
- 23 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 19 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_components” rewrote its description, which is the text the model reads security
- “search_components” reworded the description of “category” cosmetic
- 10 Sept 26 0
- New tool “compare_components” functional
- 4 Sept 26 0
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
- The server rewrote its instructions, which are the text every model session reads security
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 25 Sept 2026 · Probed https://roboparts.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roboparts.cc | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a57816fd1cd741d50e1867c0ede63849 |
| SANs: roboparts.cc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of roboparts.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| roboparts.cc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roboparts.cc/mcp | Verified | 200 | |
| http (plaintext) | http://roboparts.cc/mcp | HTTPS enforced | 301 | https://roboparts.cc/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 →
bom_compatibility_check ~229
对一组零部件（BOM，物料清单）做两两兼容性矩阵。输入已有条目 ID（可含开源贡献层 OSS-xxx），返回每个组合在 protocol/electrical/mechanical/software 四维的判定与理由。判定基于厂商公开声明字段的规则推断而非实测；未声明维度记为无法判定，不会为了填满矩阵而编造结论。返回的 verdict_reason 才是结论依据，overall_compatible=null 表示"证据不足"，不等于不兼容。
| Name | Type | Req | Description |
|---|---|---|---|
| component_ids | array | yes | 待校验的零件 ID 列表，如 ["ACT-001","SENS-001","PROTO-012"]。ID 必须真实存在：先用 search_components 取得，不要自行拼造（ID 前缀与 category 非一一对应）。支持主库零件与开源贡献层 OSS-xxx 混合。至少传 2 个才有意义。 |
No output schema declared.
No examples provided.
check_compatibility ~270
判定两个零部件在 protocol（协议）/ electrical（电气）/ mechanical（机械）/ software（ROS2）四个维度的兼容性，返回逐维结论、总体判定与置信说明。注意：结论基于厂商公开声明字段做规则推断，非实验室实测；厂商未声明的维度记为"无法判定"，既不计入兼容也不计入不兼容。
| Name | Type | Req | Description |
|---|---|---|---|
| component1_id | string | yes | 零件 1 的 ID，形如 ACT-001 / CHIP-001 / PROTO-012。请先用 search_components 取得，不要自行拼造：ID 前缀与 category 并非一一对应（例如 sensors 品类下存在 CHIP-67，platforms 下存在 ACT-patsnap-actuator；实时不一致条数见 GET /mcp 的 dataset.id_category_… |
| component2_id | string | yes | 零件 2 的 ID，取值方式同 component1_id。两个 ID 可以属于不同品类（跨品类比对正是本工具的用途）。 |
No output schema declared.
No examples provided.
compare_components ~137
并排对比 2~6 个零部件的关键参数（torque/speed/voltage/protocol/interface/weight/price），相同值自动标注，替代为同一目的连发多次 get_component_detail。缺失字段以 null 呈现，不代表不支持该特性；跨厂商数值比较请配合 get_parameter_semantics。
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | 待对比零部件 ID 数组（2~6 个），形如 ["ACT-001", "ACT-002"]。请先用 search_components 确认 ID。 |
No output schema declared.
No examples provided.
get_component_detail ~154
按 ID 获取单个零部件的完整字段，包含 source_tier（数据来源等级）、confidence（置信度）、data_quality 与 mechanical_interface 等元数据。用于在做出采购/设计决策前核对证据强度。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 零部件 ID，如 ACT-001 / CHIP-001 / SENS-001。大小写与连字符需完全匹配，不做模糊查找；建议先由 search_components 返回值取得。注意 ID 前缀不能反推 category（库内存在前缀与品类不一致的条目，实时条数见 GET /mcp 的 dataset.id_category_mismatch）。 |
No output schema declared.
No examples provided.
get_parameter_semantics ~99
获取参数口径规范：同一个 torque/speed 字段在不同厂商那里含义可能不同（库内 torque 出现 19 种口径、speed 37 种，甚至混入 Gbps 与 rad/s）。本工具返回物理红线、单位换算、可比性分级与向厂商问询的清单，用于判断两份参数表到底能不能直接比较。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_standard_audit ~133
返回标准登记表 ↔ 实体声明 的自动交叉校验结果：哪些机械/总线声明能被已知标准集核实、哪些声明的编码不在已知指定集中（无法核实），以及登记表缺口与行业标准覆盖情况。这是数据质量自检，不是兼容性裁决；其作用是指出"声明了但出处存疑"的条目，供人工补全证据。
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | 返回范围：all=完整审计报告（默认）；conflicts=仅数据质量冲突条目。 |
No output schema declared.
No examples provided.
recommend_for_application ~380
按应用场景推荐零部件组合，可选预算上限（USD）。返回各品类的候选项及推荐理由。这是基于库内字段的启发式筛选，不构成工程选型意见，最终仍需核对厂商原始数据手册。
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | 应用场景，必填，取值限 enum。判定方式是拿一组固定场景词去匹配条目的 applications/name/type/description 字段，而非人工标注的场景分类：humanoid=人形/双足，quadruped=四足，robot_arm=机械臂/协作臂，amr=移动机器人/AGV，industrial=工业产线。若某品类下无任何条目命中该场景，该品类会退化为品类罗列并在 scene_… |
| budget | number | – | 单件预算上限（USD，正数），可选。**价格字段覆盖率有限**（实时覆盖数见 GET /mcp 的 dataset.priced），因此本参数只能剔除「确定超预算」的条目，不能保证结果全部在预算内。每条结果会附 price_fit：within（确定在预算内）/ partial（区间跨越预算）/ unknown（库内无价格，未经校验）。不传则不做任何价格筛选，也不返回 price_fit。 |
| count | number | – | 每品类返回条数，默认 3，上限 10（超出按 10 截断）。四个品类各自独立计数。 |
No output schema declared.
No examples provided.
review_compatibility ~213
对两个零部件做「多 Agent 质保复核」：Worker 层执行标准四维兼容性裁决（与 /api/compatibility 同一引擎），Governor 层独立复核结论——按证据强度给出 L0–L3 风险分级、在证据不足 2 条时把"兼容"降级为"需人工确认"、对无法判定项显式列出缺失证据段。返回四维细节 + 证据契约 + governor_review。只读、免鉴权。
| Name | Type | Req | Description |
|---|---|---|---|
| component1_id | string | yes | 零件 1 的 ID，形如 ACT-001 / CHIP-001 / PROTO-012。请先用 search_components 取得，不要自行拼造。 |
| component2_id | string | yes | 零件 2 的 ID，取值方式同 component1_id。两个 ID 可以属于不同品类。 |
No output schema declared.
No examples provided.
search_components ~461
搜索机器人零部件。可按品类、关键词筛选，返回匹配条目的摘要（id/name/category/manufacturer/关键规格/证据等级）。覆盖执行器、传感器、芯片、通信协议、接口、机器人平台、具身智能模型等 20 个品类。库存实时口径（总数/可选型/已隔离）见 initialize 的 instructions 或 GET /mcp 的 dataset 字段 —— 此处不写死数字，避免文案与真实库存漂移。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 品类精确筛选，取值必须来自 enum（严格相等，不做别名映射：传 "actuator"、"电机" 均返回空）。不传则跨全部 20 个品类检索。注意品类与 ID 前缀不是一一对应的，请以本字段为准。 |
| include_market_intelligence | boolean | – | 默认 false。库内另有 3 条市场情报条目（专利地图/咨询报告/趋势条目），它们不是可采购零件，默认不返回；仅在你确实想查行业研究材料时设为 true。 |
| keyword | string | – | 关键词，对 name / name_en / manufacturer / type / protocol / interface / description 七个字段做大小写不敏感的**子串**匹配（非分词、非模糊、不纠错）。**中英文命中集合可能完全不重叠**，务必两种都试：实测 "六维力" 命中 16 条、"force torque" 命中 2 条、交集为 0（部分国产条目尚无英文名）。多… |
| limit | number | – | 返回条数上限，默认 10，最大 50（超出按 50 截断）。 |
No output schema declared.
No examples provided.
semantic_search ~230
用自然语言描述需求（如"人形机器人髋部高扭矩电机"）做语义召回，返回最相近的零部件。语义索引由离线哈希 TF-IDF 向量（构建时预计算、零外发、零外部模型）在当前全量实体上生成，是兼容性判定之外的"发现"通道：当你不确定零件的确切型号或参数名时，用它比关键词子串匹配更稳。索引不可用时自动降级为关键词检索，并明确告知。
| Name | Type | Req | Description |
|---|---|---|---|
| k | number | – | 语义召回返回的候选零部件条数（top-k），默认 5，取值 1–30；数值越大召回越广但越可能偏离查询意图。 |
| query | string | yes | 自然语言查询，如"六维力传感器 防水"或"ROS2 通信模组"。中英文均可，建议具体。 |
No output schema declared.
No examples provided.
What is the RoboParts 机器人零部件兼容性 MCP server?
RoboParts 机器人零部件兼容性 is an MCP server listed in the public MCP registry as cc.roboparts/roboparts. 688 humanoid robot component entities with 4-dimension compatibility checking. Vendor-neutral. This page covers its hosted endpoint (https://roboparts.cc/mcp).
Is the RoboParts 机器人零部件兼容性 MCP server safe to use?
RoboParts 机器人零部件兼容性 scores 77 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 RoboParts 机器人零部件兼容性 MCP server expose?
RoboParts 机器人零部件兼容性 exposes 10 tools: search_components, get_component_detail, check_compatibility, compare_components, recommend_for_application, and 5 more. Their descriptions and schemas cost roughly 2,306 tokens of context every time the server is loaded.
Does the RoboParts 机器人零部件兼容性 MCP server require authentication?
No. We connected to RoboParts 机器人零部件兼容性 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RoboParts 机器人零部件兼容性 MCP server still maintained?
RoboParts 机器人零部件兼容性 is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.