Is the Roboparts MCP server down?

mcp-registry/cc.roboparts/roboparts · v1.1.1

As of 2026-10-22 17:48 UTC, the Roboparts MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

852 humanoid/bionic robot parts, 20 categories, 4-dimension compatibility checking. Vendor-neutral.

claude mcp add --transport http roboparts-mcp-server https://roboparts.cc/mcp

{
  "mcpServers": {
    "roboparts-mcp-server": {
      "type": "http",
      "url": "https://roboparts.cc/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (83/100)

What to fix (4)

Auto-fix: 18 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcc.roboparts%2Froboparts/fixes

{
  "name": "bom_compatibility_check",
  "description": "对一组零部件（BOM，物料清单）做两两兼容性矩阵。输入已有条目 ID（可含开源贡献层 OSS-xxx），返回每个组合在 protocol/electrical/mechanical/software 四维的判定与理由。判定基于厂商公开声明字段的规则推断而非实测；未声明维度记为无法判定，不会为了填满矩阵而编造结论。返回的 verdict_reason 才是结论依据，overall_compatible=null 表示\"证据不足\"，不等于不兼容。",
  "inputSchema": {
    "type": "object",
    "required": [
      "component_ids"
    ],
    "properties": {
      "component_ids": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "待校验的零件 ID 列表，如 [\"ACT-001\",\"SENS-001\",\"PROTO-012\"]。ID 必须真实存在：先用 search_components 取得，不要自行拼造（ID 前缀与 category 非一一对应）。支持主库零件与开源贡献层 OSS-xxx 混合。至少传 2 个才有意义。"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "check_co_mount",
  "description": "查询**共装**关系（第三种关系类型，三段 A↔宿主↔B）：某个机器人本体能否同时装下两个器件（典型问题：「这台 UR5e 能同时装夹爪和六轴力传感器吗」）。与 check_compatibility 的区别：后者判「A 能不能插进 B」（二段互插），本工具判「A 和 B 能不能同时挂在同一台机器人的工具侧」。★ 三段判据：机械同型 + 宿主工具侧位数预算 + 信号角色互补。port_exhausted 表示「**装不下**（工程约束，如需转接/换本体）」，与 unknown（「数据不足，不知道」）严格区分。★ 参数：传 host+a+b 得单对裁决（附证据链）；只传 host 得该宿主的单件可装性 + 工具侧取证；不传参得全层摘要（含关系语义与示例）。只读、免鉴权。返回含 caliber 字段，口径与 check_compatibility 不同、不可混用。",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "a": {
        "type": "string",
        "description": "器件 A 的实体 id，如 ACT-028。需与 b 同时给。"
      },
      "b": {
        "type": "string",
        "description": "器件 B 的实体 id，如 SENS-047。需与 a 同时给。"
      },
      "host": {
        "type": "string",
        "description": "宿主机器人 id，如 HUB-030（UR3e）、HUB-031（UR5e）、SUPERDEX-fr3。"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "check_compatibility",
  "description": "判定两个零部件在 protocol（协议）/ electrical（电气）/ mechanical（机械）/ software（ROS2）四个维度的兼容性，返回逐维结论、总体判定与置信说明。注意：结论基于厂商公开声明字段做规则推断，非实验室实测；厂商未声明的维度记为\"无法判定\"，既不计入兼容也不计入不兼容。",
  "inputSchema": {
    "type": "object",
    "required": [
      "component1_id",
      "component2_id"
    ],
    "properties": {
      "component1_id": {
        "type": "string",
        "description": "零件 1 的 ID，形如 ACT-001 / CHIP-001 / PROTO-012。请先用 search_components 取得，不要自行拼造：ID 前缀与 category 并非一一对应（例如 sensors 品类下存在 CHIP-67，platforms 下存在 ACT-patsnap-actuator；实时不一致条数见 GET /mcp 的 dataset.id_category_mismatch），按品类猜前缀会取到错误条目或直接查无此项。"
      },
      "component2_id": {
        "type": "string",
        "description": "零件 2 的 ID，取值方式同 component1_id。两个 ID 可以属于不同品类（跨品类比对正是本工具的用途）。"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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/cc.roboparts/roboparts"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/cc.roboparts/roboparts"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~2,877 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.

Largest tool definitions

• search_components ~364 tokens
• recommend_for_application ~255 tokens
• lint_urdf ~207 tokens
• check_co_mount ~201 tokens
• explain_compose_frontier ~197 tokens

Static 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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcc.roboparts%2Froboparts.svg)](https://glimind.com/server/mcp-registry%2Fcc.roboparts%2Froboparts?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcc.roboparts%2Froboparts?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcc.roboparts%2Froboparts.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcc.roboparts%2Froboparts.svg
   :target: https://glimind.com/server/mcp-registry%2Fcc.roboparts%2Froboparts?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c6089607dd13c835…, first seen 2026-10-17, included at leaf 4092 of 47,314. Version history · verify what your client received.

Tools (20)

• bom_compatibility_check
• check_co_mount
• check_compatibility
• compare_components
• explain_compose_frontier
• explain_connector_types
• explain_evidence_cohort
• explain_evidence_mdv
• get_behavior_evidence
• get_body_binding
• get_component_detail
• get_parameter_semantics
• get_research_progress
• get_robot_tool_side
• get_standard_audit
• lint_urdf
• recommend_for_application
• review_compatibility
• search_components
• semantic_search

Compare: most reliable data servers · most reliable knowledge servers · most reliable code servers · most reliable ml servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Roboparts MCP server down right now?

As of 2026-10-22 17:48 UTC, the Roboparts MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Roboparts MCP server provide?

Roboparts MCP server advertises 20 tools, including bom_compatibility_check, check_co_mount, check_compatibility, compare_components, explain_compose_frontier.

How do I install Roboparts MCP server?

Point your MCP client at this streamable-http endpoint: https://roboparts.cc/mcp

Is the Roboparts MCP server safe to connect to an AI agent?

Glimind scanned all 20 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.

Operator of Roboparts MCP server?

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.