EcovacsSAFE
Ecovacs MCP Server
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
English | 中文
科沃斯核心API现已全面兼容MCP协议,是全球首家兼容MCP协议的机器人服务商。
科沃斯已经完成了4个核心API接口和MCP协议的对接,包括设备列表查询、清扫控制、回充控制和工作状态查询。
作为全球首家支持MCP协议的清洁机器人服务商,科沃斯MCP Server发布后,智能体开发者仅需简单配置,就可以在大模型中快速接入机器人服务,实现查询、清扫、回充等能力。
大幅降低了智能体应用开发过程中调用机器人控制服务相关能力的门槛,显著提升了智能体应用的开发效率。
工具
设备列表查询
获取用户绑定的所有机器人列表。
Input:
无参数
Returns:
{
"status": 0,
"message": "success",
"data": [
{
"nickname": "机器人昵称",
}
]
}启动清扫
控制扫地机器人开始、暂停、恢复或停止清扫。
Input:
nickname: 机器人的昵称,用于查找设备,支持模糊匹配act: 清扫行为s: 开始清扫r: 恢复清扫p: 暂停清扫h: 停止清扫
Returns:
{
"msg": "OK",
"code": 0,
"data": []
}控制回充
控制机器人开始或停止回充。
Input:
nickname: 机器人昵称,用于查找设备act: 机器行为go-start: 开始回充stopGo: 结束回充
Returns:
{
"msg": "OK",
"code": 0,
"data": []
}查询工作状态
查询机器人当前的工作状态。
Input:
nickname: 机器人昵称,用于查找设备
Returns:
{
"code": 0,
"msg": "success",
"data": {
"ctl": {
"data": {
"ret": "ok",
"cleanSt": "h",
"chargeSt": "charging",
"stationSt": "i"
}
}
}
}状态码说明:
5f3c281d360bOBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add ecovacs-mcp --env ECO_API_KEY=${ECO_API_KEY} -- uvx ecovacs-mcp{
"mcpServers": {
"ecovacs-mcp": {
"command": "uvx",
"args": [
"ecovacs-mcp"
],
"env": {
"ECO_API_KEY": "${ECO_API_KEY}"
}
}
}
}Exposed tools (2)
2 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_device_list | read | |
get_work_state | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
5f3c281d360bfull audit observations/trust-audit/mcp-server/ecovacs-ai__ecovacs.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 5f3c281d360b | SAFE | B | 89 | first audit |
Questions
What is the Ecovacs MCP server?
Ecovacs MCP Server
What tools does Ecovacs expose?
2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Ecovacs safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Ecovacs need?
It reads ECO_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Ecovacs run?
It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as ecovacs-mcp.
How current is this page?
The grade is for one exact copy of the source (5f3c281d360b), read on 2026-10-09. The repository is watched and re-audited when it changes.