mcp_server.py@r1
VERIFIED· install onlyPublisher claims: "Enables MCP clients to run three-stage drone logistics site selection, load CSV/Excel data, retrieve domain knowledge, reverse-geocode coordinates, and receive progress heartbeats for long-running tasks over stdio JSON-RPC." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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
DEEPSEEK_TOKENOPENCLAW_TOKENConfiguration, not credentials: AMAP_KEY, DEEPSEEK_BASE, DEEPSEEK_MODEL, FLASK_DEBUG, FLASK_HOST, FLASK_PORT, MCP_PROGRESS_INTERVAL_SEC, OPENCLAW_AGENT_ID, OPENCLAW_WS_URL- Where it talks to
- no vendor host named in the codeAlso deepseek.com, amap.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names deepseek.com, amap.com as well as its own vendor. The guard injects DEEPSEEK_TOKEN, OPENCLAW_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is mcp_server.py@r1 safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-12 and scored it 82/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 · 1 scenarios · 0 deviationsStatic findings
from app import ( # noqa: F401 (触发 .env 加载 + 复用样例装载逻辑)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""极简 .env 加载器：把项目根 .env 的 KEY=VALUE 读入 os.environ。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if raw.startswith(b"\xD0\xCF\x11\xE0\xA1\xB1\x1A\xE1"):Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.import app # noqa: F401 加载 .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# 先加载 .env（经 app 模块触发），再导入 agent 相关模块。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_path = Path(__file__).resolve().parent / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.