RoboParts 机器人零部件兼容性 MCP server
cc.roboparts/robopartsroboparts.ccstreamable-httpv1.1.1Scanned
852 humanoid/bionic robot parts, 20 categories, 4-dimension compatibility checking. Vendor-neutral.
26 tools: 1 can delete or cancel things, 9 change things and 16 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RoboParts 机器人零部件兼容性 MCP server can do
The RoboParts 机器人零部件兼容性 MCP server is published by roboparts.cc, a domain the MCP Registry verified. It has 26 tools. It can delete or cancel things (1 tool: cancel_task) and create or change data (9 tools: check_compatibility, recommend_for_application, bom_compatibility_check, review_compatibility and 5 more). 16 tools only read.
1 tool reads private data (get_task_status).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
26 tools
Deletes or cancels 1Claude Code: deny
cancel_task置任务取消标志位。★ stdio 无中断通道,cancel 只置标志位;任务体在下一 checkpoint 才退出。hosted 端点无跨请求任务句柄,返回 honest_note 引导到 stdio。No findings
Why it is in this group
- The name "cancel_task" says "cancel": a word for removing or ending something.
Description, as the server wrote it 置任务取消标志位。★ stdio 无中断通道,cancel 只置标志位;任务体在下一 checkpoint 才退出。hosted 端点无跨请求任务句柄,返回 honest_note 引导到 stdio。
Changes things 9Claude Code: ask
bom_compatibility_check对一组零部件(BOM,物料清单)做两两兼容性矩阵。输入已有条目 ID(可含开源贡献层 OSS-xxx),返回每个组合在 protocol/electrical/mechanical/software 四维的判定与理由。判定基于厂商公开声明字段的规则推断而非实测;未声明维度记为无法判定,不会为了填满矩阵而编造结论。返回的 verdict_reason 才是结论…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 对一组零部件(BOM,物料清单)做两两兼容性矩阵。输入已有条目 ID(可含开源贡献层 OSS-xxx),返回每个组合在 protocol/electrical/mechanical/software 四维的判定与理由。判定基于厂商公开声明字段的规则推断而非实测;未声明维度记为无法判定,不会为了填满矩阵而编造结论。返回的 verdict_reason 才是结论依据,overall_compatible=null 表示"证据不足",不等于不兼容。
check_co_mount查询**共装**关系(第三种关系类型,三段 A↔宿主↔B):某个机器人本体能否同时装下两个器件(典型问题:「这台 UR5e 能同时装夹爪和六轴力传感器吗」)。与 check_compatibility 的区别:后者判「A 能不能插进 B」(二段互插),本工具判「A 和 B 能不能同时挂在同一台机器人的工具侧」。★ 三段判据:机械同型 + 宿主工具侧位数预算 …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 查询**共装**关系(第三种关系类型,三段 A↔宿主↔B):某个机器人本体能否同时装下两个器件(典型问题:「这台 UR5e 能同时装夹爪和六轴力传感器吗」)。与 check_compatibility 的区别:后者判「A 能不能插进 B」(二段互插),本工具判「A 和 B 能不能同时挂在同一台机器人的工具侧」。★ 三段判据:机械同型 + 宿主工具侧位数预算 + 信号角色互补。port_exhausted 表示「**装不下**(工程约束,如需转接/换本体)」,与 unknown(「数据不足,不知道」)严格区分。★ 参数:传 host+a+b 得单对裁决(附证据链);只传 host 得该宿主的单件可装性 + 工具侧取证;不传参得全层摘要(含关系语义与示例)。只读、免鉴权。返回含 caliber 字段,口径与 check_compatibility 不同、不可混用。
check_compatibility判定两个零部件在 protocol(协议)/ electrical(电气)/ mechanical(机械)/ software(ROS2)四个维度的兼容性,返回逐维结论、总体判定与置信说明。注意:结论基于厂商公开声明字段做规则推断,非实验室实测;厂商未声明的维度记为"无法判定",既不计入兼容也不计入不兼容。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 判定两个零部件在 protocol(协议)/ electrical(电气)/ mechanical(机械)/ software(ROS2)四个维度的兼容性,返回逐维结论、总体判定与置信说明。注意:结论基于厂商公开声明字段做规则推断,非实验室实测;厂商未声明的维度记为"无法判定",既不计入兼容也不计入不兼容。
lint_urdf对 URDF(Unified Robot Description Format)XML 文件做静态兼容性检查。返回结构化 JSON 报告,含 severity(error/warning/info)、issues 数组、summary 与 stats。检查 10 类问题:XML 解析错误、缺失根 link、关节限位缺失、关节类型非法、重复 link 名、运动…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 对 URDF(Unified Robot Description Format)XML 文件做静态兼容性检查。返回结构化 JSON 报告,含 severity(error/warning/info)、issues 数组、summary 与 stats。检查 10 类问题:XML 解析错误、缺失根 link、关节限位缺失、关节类型非法、重复 link 名、运动学树循环、缺少 ROS 工业标准帧(flange/tool0/base)、缺少 origin、缺少 inertial 数据、mesh 路径问题。只读、免鉴权。适用于上传 URDF 到 RoboParts 前做兼容性预检。
recommend_for_application按应用场景推荐零部件组合,可选预算上限(USD)。返回各品类的候选项及推荐理由。这是基于库内字段的启发式筛选,不构成工程选型意见,最终仍需核对厂商原始数据手册。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 按应用场景推荐零部件组合,可选预算上限(USD)。返回各品类的候选项及推荐理由。这是基于库内字段的启发式筛选,不构成工程选型意见,最终仍需核对厂商原始数据手册。
review_compatibility对两个零部件做「多 Agent 质保复核」:Worker 层执行标准四维兼容性裁决(与 /api/compatibility 同一引擎),Governor 层独立复核结论——按证据强度给出 L0–L3 风险分级、在证据不足 2 条时把"兼容"降级为"需人工确认"、对无法判定项显式列出缺失证据段。返回四维细节 + 证据契约 + governor_review。…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 对两个零部件做「多 Agent 质保复核」:Worker 层执行标准四维兼容性裁决(与 /api/compatibility 同一引擎),Governor 层独立复核结论——按证据强度给出 L0–L3 风险分级、在证据不足 2 条时把"兼容"降级为"需人工确认"、对无法判定项显式列出缺失证据段。返回四维细节 + 证据契约 + governor_review。只读、免鉴权。
start_long_task启动长任务并返回任务句柄。★ hosted 端点(Cloudflare Workers)无跨请求内存持久化,任务句柄只在 stdio npm 包 (roboparts-mcp-server)里可用。本端点返回 honest_note 引导到 stdio 模式,不假装能保存跨请求任务。No findings
Why it is in this group
- The name "start_long_task" says "start": a word for a change.
Description, as the server wrote it 启动长任务并返回任务句柄。★ hosted 端点(Cloudflare Workers)无跨请求内存持久化,任务句柄只在 stdio npm 包 (roboparts-mcp-server)里可用。本端点返回 honest_note 引导到 stdio 模式,不假装能保存跨请求任务。
trace_export导出调用轨迹(默认去敏)。★ hosted 端点无跨请求内存持久化,trace 环形缓冲只在 stdio npm 包可用。本端点返回 honest_note 引导到 stdio 模式;stdio 支持 ROBOPARTS_TRACE_FILE 环境变量落盘 JSONL 供事后回放。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 导出调用轨迹(默认去敏)。★ hosted 端点无跨请求内存持久化,trace 环形缓冲只在 stdio npm 包可用。本端点返回 honest_note 引导到 stdio 模式;stdio 支持 ROBOPARTS_TRACE_FILE 环境变量落盘 JSONL 供事后回放。
trace_replay从 JSONL 文本重放轨迹(结构校验 + 计数)。本端点可处理**当前请求内传入的** json_lines;不做"重算 verdict"(语义重放属 P3,需要完整输入重演)。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 从 JSONL 文本重放轨迹(结构校验 + 计数)。本端点可处理**当前请求内传入的** json_lines;不做"重算 verdict"(语义重放属 P3,需要完整输入重演)。
Only reads 16Show 16 read-only tools
compare_components并排对比 2~6 个零部件的关键参数(torque/speed/voltage/protocol/interface/weight/price),相同值自动标注,替代为同一目的连发多次 get_component_detail。缺失字段以 null 呈现,不代表不支持该特性;跨厂商数值比较请配合 get_parameter_semantics。No findings
Why it is in this group
- The name "compare_components" says "compare": a word for reading.
Description, as the server wrote it 并排对比 2~6 个零部件的关键参数(torque/speed/voltage/protocol/interface/weight/price),相同值自动标注,替代为同一目的连发多次 get_component_detail。缺失字段以 null 呈现,不代表不支持该特性;跨厂商数值比较请配合 get_parameter_semantics。
explain_compose_frontier【研究层口径 · 与 check_compatibility 的四维不同】查询 RoboParts 三轴组合判定(mechanical 机械 / electrical 电气 / signal 信号角色)的现算结论:整体 composed/type_error/unknown、逐轴裁决与理由,以及「为什么 composed 通常为 0」的归因(L1 跨角色 →…No findings
Why it is in this group
- The name "explain_compose_frontier" says "explain": a word for reading.
Description, as the server wrote it 【研究层口径 · 与 check_compatibility 的四维不同】查询 RoboParts 三轴组合判定(mechanical 机械 / electrical 电气 / signal 信号角色)的现算结论:整体 composed/type_error/unknown、逐轴裁决与理由,以及「为什么 composed 通常为 0」的归因(L1 跨角色 → L2 机械可判定 → L3 全轴可判定的三层分解)。适合回答「这两个零件为什么判为 type_error」「哪些配对能真的装起来」「composed=0 是数据缺口还是关系类型问题」。只读、免鉴权。**注意口径差异**:本工具用 signal 角色互补(执行器↔传感器),check_compatibility 用 protocol 总线 + ROS2 支持,两者维度不同不可混用。
explain_connector_types【研究层口径】查询连接器取证与类型判据:已核实的连接器(针数/针序/供电)、「同族不同变体」的不可互插案例,以及 (family, pins, pinout) 三元组判据。适合回答「这两个连接器能不能互插」「同为 M8 为什么判不兼容」「pinout 为 null 是什么意思」。只读、免鉴权。No findings
Why it is in this group
- The name "explain_connector_types" says "explain": a word for reading.
Description, as the server wrote it 【研究层口径】查询连接器取证与类型判据:已核实的连接器(针数/针序/供电)、「同族不同变体」的不可互插案例,以及 (family, pins, pinout) 三元组判据。适合回答「这两个连接器能不能互插」「同为 M8 为什么判不兼容」「pinout 为 null 是什么意思」。只读、免鉴权。
explain_evidence_cohort【研究层口径】查询「最小可行同质集」取证判据:补哪一条数据最值、为什么单条声明的边际收益为 0、以及应按缺口画像批量取证的顺序。适合回答「取证该从哪开始」「补机械声明率有没有用」「K=2 是什么意思」。只读、免鉴权。No findings
Why it is in this group
- The name "explain_evidence_cohort" says "explain": a word for reading.
Description, as the server wrote it 【研究层口径】查询「最小可行同质集」取证判据:补哪一条数据最值、为什么单条声明的边际收益为 0、以及应按缺口画像批量取证的顺序。适合回答「取证该从哪开始」「补机械声明率有没有用」「K=2 是什么意思」。只读、免鉴权。
explain_evidence_mdv【研究层口径】查询边际声明价值(MDV):各轴未声明节点的零贡献率、哪些取证方向边际收益恒为 0、以及瓶颈轴是哪个。适合回答「补哪个轴最划算」「某个轴还有取证价值吗」。只读、免鉴权。口径与 check_compatibility 不同,不可混用。No findings
Why it is in this group
- The name "explain_evidence_mdv" says "explain": a word for reading.
Description, as the server wrote it 【研究层口径】查询边际声明价值(MDV):各轴未声明节点的零贡献率、哪些取证方向边际收益恒为 0、以及瓶颈轴是哪个。适合回答「补哪个轴最划算」「某个轴还有取证价值吗」。只读、免鉴权。口径与 check_compatibility 不同,不可混用。
explain_unknown结构化解释「为什么某次判定是 unknown」。三种模式:① component_id + category → 返回该实体的 evidence_gaps / null 字段清单;② verdict_id → 反查当前请求内的判定(hosted 端点无跨请求会话,仅回当前请求);③ 无参 → 返回全库 unknown 覆盖率摘要。★ 口径纪律:字段级扫描 ≠…No findings
Why it is in this group
- The name "explain_unknown" says "explain": a word for reading.
Description, as the server wrote it 结构化解释「为什么某次判定是 unknown」。三种模式:① component_id + category → 返回该实体的 evidence_gaps / null 字段清单;② verdict_id → 反查当前请求内的判定(hosted 端点无跨请求会话,仅回当前请求);③ 无参 → 返回全库 unknown 覆盖率摘要。★ 口径纪律:字段级扫描 ≠ 因果归因(后者属 gap_classification 研究层)。只读、免鉴权。
get_behavior_evidence查询**行为证据**:开源 VLA 在真机上的 benchmark 成功率(引用论文/官方报告,**非本仓自造日志**——本项目按锚点禁止造仿真器/训练栈)。适合回答「GR00T 真机成功率多少」「SmolVLA 有实测数据吗」「仿真成绩能不能当真机用」。★ 三条纪律:① 仿真(sim)与真机(real)**严格分列**,不可合并统计;② 只收录**有对照组…No findings
Why it is in this group
- The name "get_behavior_evidence" says "get": a word for reading.
Description, as the server wrote it 查询**行为证据**:开源 VLA 在真机上的 benchmark 成功率(引用论文/官方报告,**非本仓自造日志**——本项目按锚点禁止造仿真器/训练栈)。适合回答「GR00T 真机成功率多少」「SmolVLA 有实测数据吗」「仿真成绩能不能当真机用」。★ 三条纪律:① 仿真(sim)与真机(real)**严格分列**,不可合并统计;② 只收录**有对照组**的数字(孤证可能是 cherry-pick);③ 官方未报告的指标 value=null,不折算。样本量官方均未报告 ⇒ 不可用于统计比较。只读、免鉴权。
get_body_binding查询**开源 VLA → 机器人本体**的绑定及其强度分档。强度四档:validated(论文明写真机评测跑在该本体)/ family(论文列该族)/ adaptable(官方称可微调,非特定硬件验证)/ category_only(只登记类别)。另有两个**非绑定态**:blocked_missing_body(依据充分但本体不在库内)与 category…No findings
Why it is in this group
- The name "get_body_binding" says "get": a word for reading.
Description, as the server wrote it 查询**开源 VLA → 机器人本体**的绑定及其强度分档。强度四档:validated(论文明写真机评测跑在该本体)/ family(论文列该族)/ adaptable(官方称可微调,非特定硬件验证)/ category_only(只登记类别)。另有两个**非绑定态**:blocked_missing_body(依据充分但本体不在库内)与 category_only。适合回答「OpenVLA 能装在哪台机器人上」「这个绑定可信吗」「为什么 SmolVLA 没有 body_robot」。★ 只绑开源 VLA——闭源模型无公开验证栈,不编造绑定。只读、免鉴权。
get_component_detail按 ID 获取单个零部件的完整字段,包含 source_tier(数据来源等级)、confidence(置信度)、data_quality 与 mechanical_interface 等元数据。用于在做出采购/设计决策前核对证据强度。No findings
Why it is in this group
- The name "get_component_detail" says "get": a word for reading.
Description, as the server wrote it 按 ID 获取单个零部件的完整字段,包含 source_tier(数据来源等级)、confidence(置信度)、data_quality 与 mechanical_interface 等元数据。用于在做出采购/设计决策前核对证据强度。
get_parameter_semantics获取参数口径规范:同一个 torque/speed 字段在不同厂商那里含义可能不同(库内 torque 出现 19 种口径、speed 37 种,甚至混入 Gbps 与 rad/s)。本工具返回物理红线、单位换算、可比性分级与向厂商问询的清单,用于判断两份参数表到底能不能直接比较。No findings
Why it is in this group
- The name "get_parameter_semantics" says "get": a word for reading.
Description, as the server wrote it 获取参数口径规范:同一个 torque/speed 字段在不同厂商那里含义可能不同(库内 torque 出现 19 种口径、speed 37 种,甚至混入 Gbps 与 rad/s)。本工具返回物理红线、单位换算、可比性分级与向厂商问询的清单,用于判断两份参数表到底能不能直接比较。
get_research_progress查询「核心目标完成度」的可复现判据:把核心目标(脑×体×智做成机器可校验的组合 + 全链路可溯源)拆成四个维度的分项,每项给出分子/分母/口径/剩余缺口,并报出门控与朴素两个口径的加权完成度。适合回答「这个项目做到什么程度了」「核心目标完成了几成」「composed 为什么是 0」。只读、免鉴权。★ 口径警告:这是**一个口径**下的数字,不是客观测量;权重…No findings
Why it is in this group
- The name "get_research_progress" says "get": a word for reading.
Description, as the server wrote it 查询「核心目标完成度」的可复现判据:把核心目标(脑×体×智做成机器可校验的组合 + 全链路可溯源)拆成四个维度的分项,每项给出分子/分母/口径/剩余缺口,并报出门控与朴素两个口径的加权完成度。适合回答「这个项目做到什么程度了」「核心目标完成了几成」「composed 为什么是 0」。只读、免鉴权。★ 口径警告:这是**一个口径**下的数字,不是客观测量;权重可争议;且采用**门控口径**——核心判据(composed)为 0 时 body 维记 0,因为「判定基础设施建成」不等于「组合成立」。
get_robot_tool_side查询机器人本体的**工具侧接口取证**:工具法兰(ISO 9409-1 标号)、工具 I/O 位数、连接器型号与承载信号。适合回答「这台机器人工具侧有几个电气接口」「tool_io_ports 为什么是 null」「UR 的工具侧能挂几个传感器」。★ tool_io_ports 是**一手取证的整数位计数**(不是针数);未取证者留 null,判据据此走 u…No findings
Why it is in this group
- The name "get_robot_tool_side" says "get": a word for reading.
Description, as the server wrote it 查询机器人本体的**工具侧接口取证**:工具法兰(ISO 9409-1 标号)、工具 I/O 位数、连接器型号与承载信号。适合回答「这台机器人工具侧有几个电气接口」「tool_io_ports 为什么是 null」「UR 的工具侧能挂几个传感器」。★ tool_io_ports 是**一手取证的整数位计数**(不是针数);未取证者留 null,判据据此走 unknown,**不按型号名推断**。只读、免鉴权。
get_standard_audit返回标准登记表 ↔ 实体声明 的自动交叉校验结果:哪些机械/总线声明能被已知标准集核实、哪些声明的编码不在已知指定集中(无法核实),以及登记表缺口与行业标准覆盖情况。这是数据质量自检,不是兼容性裁决;其作用是指出"声明了但出处存疑"的条目,供人工补全证据。No findings
Why it is in this group
- The name "get_standard_audit" says "get": a word for reading.
Description, as the server wrote it 返回标准登记表 ↔ 实体声明 的自动交叉校验结果:哪些机械/总线声明能被已知标准集核实、哪些声明的编码不在已知指定集中(无法核实),以及登记表缺口与行业标准覆盖情况。这是数据质量自检,不是兼容性裁决;其作用是指出"声明了但出处存疑"的条目,供人工补全证据。
get_task_status查询长任务状态。★ hosted 端点无跨请求任务句柄,返回 honest_note 引导到 stdio 模式。Reads private dataNo findings
Why it is in this group
- The name "get_task_status" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Description, as the server wrote it 查询长任务状态。★ hosted 端点无跨请求任务句柄,返回 honest_note 引导到 stdio 模式。
search_components搜索机器人零部件。可按品类、关键词筛选,返回匹配条目的摘要(id/name/category/manufacturer/关键规格/证据等级)。覆盖执行器、传感器、芯片、通信协议、接口、机器人平台、具身智能模型等 20 个品类。库存实时口径(总数/可选型/已隔离)见 initialize 的 instructions 或 GET /mcp 的 dataset …No findings
Why it is in this group
- The name "search_components" says "search": a word for reading.
Description, as the server wrote it 搜索机器人零部件。可按品类、关键词筛选,返回匹配条目的摘要(id/name/category/manufacturer/关键规格/证据等级)。覆盖执行器、传感器、芯片、通信协议、接口、机器人平台、具身智能模型等 20 个品类。库存实时口径(总数/可选型/已隔离)见 initialize 的 instructions 或 GET /mcp 的 dataset 字段 —— 此处不写死数字,避免文案与真实库存漂移。
semantic_search用自然语言描述需求(如"人形机器人髋部高扭矩电机")做语义召回,返回最相近的零部件。语义索引由离线哈希 TF-IDF 向量(构建时预计算、零外发、零外部模型)在当前全量实体上生成,是兼容性判定之外的"发现"通道:当你不确定零件的确切型号或参数名时,用它比关键词子串匹配更稳。索引不可用时自动降级为关键词检索,并明确告知。No findings
Why it is in this group
- The name "semantic_search" says "search": a word for reading.
Description, as the server wrote it 用自然语言描述需求(如"人形机器人髋部高扭矩电机")做语义召回,返回最相近的零部件。语义索引由离线哈希 TF-IDF 向量(构建时预计算、零外发、零外部模型)在当前全量实体上生成,是兼容性判定之外的"发现"通道:当你不确定零件的确切型号或参数名时,用它比关键词子串匹配更稳。索引不可用时自动降级为关键词检索,并明确告知。
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 10
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 10 tools that change things (1 destructive, 9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://roboparts.cc/mcp: tools/list returned 26 tools to an anonymous client, including cancel_task (destructive), check_compatibility (write), recommend_for_application (write), bom_compatibility_check (write), review_compatibility (write) and 5 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 6 to 10
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 10.View diff
- Tools that change things, listed without credentials: 6 to 10
Tools6 added.+6 addedView diff
- Added:cancel_taskDeletes or cancels
- Added:explain_unknownOnly reads
- Added:get_task_statusOnly reads
- Added:start_long_taskChanges things
- Added:trace_exportChanges things
- Added:trace_replayChanges things
Install
Pinned to version 1.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http roboparts https://roboparts.cc/mcpclaude mcp add --transport http roboparts https://roboparts.cc/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__roboparts__search_components",
"mcp__roboparts__get_component_detail",
"mcp__roboparts__compare_components",
"mcp__roboparts__get_parameter_semantics",
"mcp__roboparts__semantic_search",
"mcp__roboparts__get_standard_audit",
"mcp__roboparts__explain_compose_frontier",
"mcp__roboparts__explain_evidence_cohort",
"mcp__roboparts__explain_evidence_mdv",
"mcp__roboparts__explain_connector_types",
"mcp__roboparts__get_research_progress",
"mcp__roboparts__get_robot_tool_side",
"mcp__roboparts__get_behavior_evidence",
"mcp__roboparts__get_body_binding",
"mcp__roboparts__explain_unknown",
"mcp__roboparts__get_task_status"
],
"ask": [
"mcp__roboparts__check_compatibility",
"mcp__roboparts__recommend_for_application",
"mcp__roboparts__bom_compatibility_check",
"mcp__roboparts__review_compatibility",
"mcp__roboparts__lint_urdf",
"mcp__roboparts__check_co_mount",
"mcp__roboparts__start_long_task",
"mcp__roboparts__trace_export",
"mcp__roboparts__trace_replay"
],
"deny": [
"mcp__roboparts__cancel_task"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as roboparts. Review it before you use it.
Capability tags behind 1 rule
- mcp__roboparts__get_task_status private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/cc.roboparts/roboparts/verify?hash=ac7b77b9573c974fdb1cea77c0b89423c541f38b4a95723b8b6d8d81c00af0bd" | jq -e '.changed == false'Pinned hash ac7b77b9573c, from Nov 10, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/cc.roboparts/roboparts/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/cc.roboparts/roboparts)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:46 UTC.
RoboParts 机器人零部件兼容性 MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RoboParts 机器人零部件兼容性 MCP server safe?
- No scan can promise that. What its definitions show: 26 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RoboParts 机器人零部件兼容性 MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_task.
Can the RoboParts 机器人零部件兼容性 MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the RoboParts 机器人零部件兼容性 MCP server have?
- 26 tools: 1 destructive, 9 write, 16 read. cancel_task, check_compatibility, recommend_for_application, bom_compatibility_check, review_compatibility, lint_urdf, check_co_mount, start_long_task and 18 more.
Does the RoboParts 机器人零部件兼容性 MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RoboParts 机器人零部件兼容性 MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the RoboParts 机器人零部件兼容性 MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.