RobotScope MCP Server
REMOTE · MCP.ROBOTSCOPE.NET
Embodied AI & robotics MCP — 180+ companies, funding, Pulse, sector data (CC BY-NC 4.0)
Available components
Last scanned (46 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 27 Aug 2026.
Category IoT and Hardware
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 3 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass 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 3 Sept 2026 · Probed https://mcp.robotscope.net/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.robotscope.net. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.robotscope.net. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.robotscope.net/mcp | Unreachable | ||
| http (plaintext) | http://mcp.robotscope.net/mcp | HTTPS enforced |
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 →
compare_companies ~90
同时拉 1-5 家公司的核心 meta 用于对比（融资/估值/成立/阶段/产业链位置）。传 1 家返回单项摘要，2+ 家返回并排表格友好结构。支持别名。
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | 1-5 家公司 slug 或别名，如 ["agibot", "宇树"] |
No output schema declared.
No examples provided.
get_changelog ~128
获取【单家公司】「动态记录」section 的变更时间线（非全局 changelog）。slug 为必填参数，指定目标公司。返回该公司最近 N 天的动态摘要，用于回答"这家公司最近有什么变化"。如需多家公司动态，请使用 search_companies 或 list_recent_updates。
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | 返回最近 N 天的记录，默认 30 天 |
| slug | string | yes | 公司 slug 或别名，如 "unitree" / "figure-ai" / "agibot"。支持别名映射。 |
No output schema declared.
No examples provided.
get_company_detail ~106
获取单家公司完整档案（团队/产品/技术路线/商业进展/融资/风险），含 markdown 内容。支持别名：如 "agibot"→智元机器人、"宇树"→unitree。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 公司 slug 或别名，如 "figure-ai" / "unitree" / "agibot"（自动映射到 zhiyuan-robotics）。可先用 search_companies 找 slug。 |
No output schema declared.
No examples provided.
get_funding_summary ~43
返回 robotscope 188+ 家公司融资格局摘要 — 总融资规模 / 国家分布 / 产业链分布 / 估值分布。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pulse ~82
获取 RobotScope 每日具身智能简报 Pulse 的卡片数据。每条含标题/分类/摘要/判断/关联公司。用于"今天具身智能圈发生了什么"。
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | 日期 YYYY-MM-DD，默认最新一期 |
| limit | number | – | 返回前 N 条卡片，默认全部 |
No output schema declared.
No examples provided.
industry_landscape ~46
返回具身智能产业链全景图（感知层/运动控制层/具身本体层/智能层/应用层），每层下公司清单。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recent_updates ~47
列出最近 N 天 profile 有更新的公司（last_updated 在 N 天内）。用于"昨天/本周行业有啥动静"
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
No output schema declared.
No examples provided.
search_by_sector ~152
按赛道/技术路线筛选公司。支持中英文赛道名（如"人形机器人"/"灵巧手"/"VLA"/"仓储物流"/"减速器"/"四足"）。从 tags + layer + name + chinese_name 中智能匹配，返回匹配的公司列表及赛道统计。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| sector | string | yes | 赛道名，如 "人形机器人" / "灵巧手" / "VLA" / "仓储物流" / "减速器" / "四足机器人" / "具身基础模型" / "世界模型" / "工业自动化" |
No output schema declared.
No examples provided.
search_companies ~297
在 robotscope 188+ 家具身智能公司中搜索。支持中英文关键词、常见别名（如"宇树"→Unitree、"figure"→Figure AI）、模糊匹配。可叠加 filter（国家/产业链层/优先级/估值范围）。支持按估值排序。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | 国家筛选，支持 ISO 代码（"CN"/"US"/"UK"/"DE"/"FR"/"KR"/"JP"）或全称（"China"/"United States"/"Germany"），自动归一化 |
| layer | string | – | 产业链层筛选，如 "具身本体层" / "智能层" / "感知层" |
| limit | number | – | – |
| priority | string | – | – |
| query | string | – | 关键词，匹配公司名 / 中文名 / 标签 / 产业链位置 / 国家。支持别名（如"宇树""figure""优必选"）。留空则仅按 filter 条件搜索。 |
| sort_by | string | – | 排序方式，默认 relevance |
| valuation_max | number | – | 最高估值（美元），如 5e9 = 50亿美元 |
| valuation_min | number | – | 最低估值（美元），如 1e9 = 10亿美元 |
No output schema declared.
No examples provided.
How do I install the RobotScope MCP Server server?
RobotScope MCP Server is a hosted endpoint at https://mcp.robotscope.net/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 · mcp.robotscope.net
claude mcp add --transport http net-robotscope-mcp 'https://mcp.robotscope.net/mcp'
What is the RobotScope MCP Server server?
RobotScope MCP Server is listed in the public MCP registry as net.robotscope/mcp. Embodied AI & robotics MCP, 180+ companies, funding, Pulse, sector data (CC BY-NC 4.0). This page covers its hosted endpoint (https://mcp.robotscope.net/mcp).
Is the RobotScope MCP Server server safe to use?
RobotScope MCP Server scores 0 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 RobotScope MCP Server server expose?
RobotScope MCP Server exposes 9 tools: search_companies, get_company_detail, compare_companies, industry_landscape, list_recent_updates, and 4 more. Their descriptions and schemas cost roughly 991 tokens of context every time the server is loaded.
Does the RobotScope MCP Server server require authentication?
Its publisher declares no required credentials for RobotScope MCP Server. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the RobotScope MCP Server server still maintained?
RobotScope MCP Server has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 27 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.