RoboParts 机器人零部件兼容性
REMOTE · ROBOPARTS.CC · SCANNED AUG 8
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 →
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 5 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 Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1637 tokens (~327/item across 5 items; 5 tools + 0 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · roboparts.cc
claude mcp add --transport http cc-roboparts-roboparts 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": {
"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.
- 7 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Aug 26 −1
- Schema quality: 197 → 327 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “check_compatibility” reworded the description of “component1_id” cosmetic
- “check_compatibility” reworded the description of “component2_id” cosmetic
- “get_component_detail” reworded the description of “id” cosmetic
- “recommend_for_application” reworded the description of “application” cosmetic
- “recommend_for_application” reworded the description of “count” cosmetic
- “search_components” reworded the description of “category” cosmetic
- “search_components” reworded the description of “keyword” cosmetic
- “search_components” reworded the description of “limit” cosmetic
- “recommend_for_application” reworded the description of “budget” cosmetic
- 5 Aug 26 59
First indexed and scored.
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 8 Aug 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 | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 3f245ac4b1ad34c90e06575552ef3720 |
| 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 |
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 |
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.
check_compatibility ~262
判定两个零部件在 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 并非一一对应（688 条中有 38 条不一致，例如 sensors 品类下存在 CHIP-67，platforms 下存在 ACT-patsnap-actuator），按品类猜前缀会取到错误条目或直接查无此项。 |
| component2_id | string | yes | 零件 2 的 ID，取值方式同 component1_id。两个 ID 可以属于不同品类（跨品类比对正是本工具的用途）。 |
No output schema declared.
No examples provided.
get_component_detail ~133
按 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（688 条中 38 条不一致）。 |
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.
recommend_for_application ~376
按应用场景推荐零部件组合，可选预算上限（USD）。返回各品类的候选项及推荐理由。这是基于库内字段的启发式筛选，不构成工程选型意见，最终仍需核对厂商原始数据手册。
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | 应用场景，必填，取值限 enum。判定方式是拿一组固定场景词去匹配条目的 applications/name/type/description 字段，而非人工标注的场景分类：humanoid=人形/双足，quadruped=四足，robot_arm=机械臂/协作臂，amr=移动机器人/AGV，industrial=工业产线。若某品类下无任何条目命中该场景，该品类会退化为品类罗列并在 scene_… |
| budget | number | – | 单件预算上限（USD，正数），可选。**覆盖率有限：688 条中仅 194 条带价格字段**，因此本参数只能剔除「确定超预算」的条目，不能保证结果全部在预算内。每条结果会附 price_fit：within（确定在预算内）/ partial（区间跨越预算）/ unknown（库内无价格，未经校验）。不传则不做任何价格筛选，也不返回 price_fit。 |
| count | number | – | 每品类返回条数，默认 3，上限 10（超出按 10 截断）。四个品类各自独立计数。 |
No output schema declared.
No examples provided.
search_components ~423
搜索机器人零部件。可按品类、关键词筛选，返回匹配条目的摘要（id/name/category/manufacturer/关键规格/证据等级）。库内共 688 条实体，覆盖执行器、传感器、芯片、通信协议、接口、机器人平台、具身智能模型等 10 个品类。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 品类精确筛选，取值必须来自 enum（严格相等，不做别名映射：传 "actuator"、"电机" 均返回空）。不传则跨全部 10 个品类检索。注意品类与 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.