Skills/PyPI/roboteditmcp

roboteditmcp@0.2.2

VERIFIED· not started

Publisher claims: "MCP server for Robot configuration management - AI Agent tools for Robot draft/online/template configs" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher huruize · publishing for 243 daysInstalls 96Last detonated 1 h ago
$claude mcp add roboteditmcp -- uvx roboteditmcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
ROBOT_ADMIN_TOKENConfiguration, not credentials: API_TIMEOUT, MAX_CONNECTIONS, ROBOT_BASE_URL, ROBOT_LOG_LEVEL, TF_NAMESPACE, TF_ROBOT_ID
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for ROBOT_ADMIN_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx roboteditmcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-16 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsCLAUDE.md:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file paths.claude/agents/pytest-case-writer.md:35 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- Create .env.test files for test-specific configurationFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsCLAUDE.md:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# 编辑 .env 文件,填入必需的环境变量:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsCLAUDE.md:22 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# 从示例创建 .env 文件Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file paths.claude/agents/pytest-case-writer.md:51 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Load test environment variables from .env.test"""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsCLAUDE.md:176 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- 从 `.env` 文件加载环境变量(不在 git 中)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:21 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file = project_root / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Remote installer piped to shell.github/workflows/publish.yml:30 · Remote installer piped to shellcurl -LsSf https://astral.sh/uv/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST07
MEDIUM
Access to sensitive file pathstests/conftest.py:36 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filespytest.skip(f".env file not found at {env_file}", allow_module_level=True)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:13 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Load environment variables from .env file before running tests.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:15 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesThis fixture automatically loads environment variables from the .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Pipe-to-shell pattern.github/workflows/publish.yml:30 · Pipe-to-shell pattern — downloads and immediately executes remote codecurl -LsSf https://astral.sh/uv/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST06
MEDIUM
Access to sensitive file pathstests/api/prepare_online_config.py:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- 需要设置正确的环境变量 (.env 文件)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Read the .env file and set environment variablesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈6,178 tok
4 files · 69 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.