Connect RoboParts 机器人零部件兼容性 and your agent gets 10 tools, among them bom_compatibility_check, check_compatibility, compare_components. It answers at https://roboparts.cc/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
852 humanoid/bionic robot parts, 20 categories, 4-dimension compatibility checking. Vendor-neutral.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
bom_compatibility_check | 对一组零部件（BOM，物料清单）做两两兼容性矩阵。输入已有条目 ID（可含开源贡献层 OSS-xxx），返回每个组合在 protocol/electrical/mechanical/software 四维的判定与理由。判定基于厂商公开声明字段的规则推断而非实测；未声明维度记为无法判定，不会为了填满矩阵而编造结论。返回的 verdict_reason 才是结论依据，overall_compatible=null 表示"证据不足"，不等于不兼容。 Inputs: component_ids |
check_compatibility | 判定两个零部件在 protocol（协议）/ electrical（电气）/ mechanical（机械）/ software（ROS2）四个维度的兼容性，返回逐维结论、总体判定与置信说明。注意：结论基于厂商公开声明字段做规则推断，非实验室实测；厂商未声明的维度记为"无法判定"，既不计入兼容也不计入不兼容。 Inputs: component1_id, component2_id |
compare_components | 并排对比 2~6 个零部件的关键参数（torque/speed/voltage/protocol/interface/weight/price），相同值自动标注，替代为同一目的连发多次 get_component_detail。缺失字段以 null 呈现，不代表不支持该特性；跨厂商数值比较请配合 get_parameter_semantics。 Inputs: ids |
get_component_detail | 按 ID 获取单个零部件的完整字段，包含 source_tier（数据来源等级）、confidence（置信度）、data_quality 与 mechanical_interface 等元数据。用于在做出采购/设计决策前核对证据强度。 Inputs: id |
get_parameter_semantics | 获取参数口径规范：同一个 torque/speed 字段在不同厂商那里含义可能不同（库内 torque 出现 19 种口径、speed 37 种，甚至混入 Gbps 与 rad/s）。本工具返回物理红线、单位换算、可比性分级与向厂商问询的清单，用于判断两份参数表到底能不能直接比较。 |
get_standard_audit | 返回标准登记表 ↔ 实体声明 的自动交叉校验结果：哪些机械/总线声明能被已知标准集核实、哪些声明的编码不在已知指定集中（无法核实），以及登记表缺口与行业标准覆盖情况。这是数据质量自检，不是兼容性裁决；其作用是指出"声明了但出处存疑"的条目，供人工补全证据。 Inputs: scope |
recommend_for_application | 按应用场景推荐零部件组合，可选预算上限（USD）。返回各品类的候选项及推荐理由。这是基于库内字段的启发式筛选，不构成工程选型意见，最终仍需核对厂商原始数据手册。 Inputs: application, budget, count |
review_compatibility | 对两个零部件做「多 Agent 质保复核」：Worker 层执行标准四维兼容性裁决（与 /api/compatibility 同一引擎），Governor 层独立复核结论——按证据强度给出 L0–L3 风险分级、在证据不足 2 条时把"兼容"降级为"需人工确认"、对无法判定项显式列出缺失证据段。返回四维细节 + 证据契约 + governor_review。只读、免鉴权。 Inputs: component1_id, component2_id |
search_components | 搜索机器人零部件。可按品类、关键词筛选，返回匹配条目的摘要（id/name/category/manufacturer/关键规格/证据等级）。覆盖执行器、传感器、芯片、通信协议、接口、机器人平台、具身智能模型等 10 个品类。库存实时口径（总数/可选型/已隔离）见 initialize 的 instructions 或 GET /mcp 的 dataset 字段 —— 此处不写死数字，避免文案与真实库存漂移。 Inputs: category, keyword, limit, include_market_intelligence |
semantic_search | 用自然语言描述需求（如"人形机器人髋部高扭矩电机"）做语义召回，返回最相近的零部件。语义索引由离线哈希 TF-IDF 向量（构建时预计算、零外发、零外部模型）在当前全量实体上生成，是兼容性判定之外的"发现"通道：当你不确定零件的确切型号或参数名时，用它比关键词子串匹配更稳。索引不可用时自动降级为关键词检索，并明确告知。 Inputs: query, k |
Every block below points at https://roboparts.cc/mcp. Pick your client and copy.
claude mcp add --transport http roboparts https://roboparts.cc/mcp
{
"mcpServers": {
"roboparts": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://roboparts.cc/mcp"]
}
}
}{
"mcpServers": {
"roboparts": {
"url": "https://roboparts.cc/mcp"
}
}
}{
"servers": {
"roboparts": {
"type": "http",
"url": "https://roboparts.cc/mcp"
}
}
}{
"context_servers": {
"roboparts": {
"url": "https://roboparts.cc/mcp"
}
}
}{
"mcpServers": {
"roboparts": {
"serverUrl": "https://roboparts.cc/mcp"
}
}
}{
"mcpServers": {
"roboparts": {
"url": "https://roboparts.cc/mcp"
}
}
}name: RoboParts 机器人零部件兼容性
version: 0.0.1
schema: v1
mcpServers:
- name: RoboParts 机器人零部件兼容性
type: streamable-http
url: https://roboparts.cc/mcp{
"mcpServers": {
"roboparts": {
"httpUrl": "https://roboparts.cc/mcp"
}
}
}{
"mcpServers": {
"roboparts": {
"type": "http",
"url": "https://roboparts.cc/mcp"
}
}
}{
"mcpServers": {
"roboparts": {
"url": "https://roboparts.cc/mcp"
}
}
}goose://extension?url=https%3A%2F%2Froboparts.cc%2Fmcp&type=streamable_http&id=roboparts&name=RoboParts%20%E6%9C%BA%E5%99%A8%E4%BA%BA%E9%9B%B6%E9%83%A8%E4%BB%B6%E5%85%BC%E5%AE%B9%E6%80%A7
It answered our last check on 17 October 2026 in 483 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by roboparts.cc and served from roboparts.cc, the vendor's own domain: https://roboparts.cc/mcp.
10, as returned by the server's own tools/list on 9 September 2026: bom_compatibility_check, check_compatibility, compare_components, get_component_detail, get_parameter_semantics, get_standard_audit, recommend_for_application, review_compatibility, and 2 more.
It answered our last check on 17 October 2026 in 483 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://roboparts.cc/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: cc.roboparts. Endpoint host: roboparts.cc. ARD identifier: urn:air:cc.roboparts:mcp:roboparts.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.