reolink-mcp@1.0.0
VERIFIED· not startedPublisher claims: "MCP server for Reolink cameras: snapshots, device state, AI detection, PTZ, and deterrence controls over the local network." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
- no credential variables read in the code
- 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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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-15 and scored it 84/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 deviationsStatic findings
f"the matching .env var"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Usage (from the repo root, reusing Phase 1's existing config.yaml/.env):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# `tmp_config` below). On a developer machine whose `.env` holds realFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"the matching .env var"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""os.environ merged with the repo .env (env wins, matching the server)."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.problems.append(f" {var} is not set (add it to .env)")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Usage (from the repo root, after filling in config.yaml and .env):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# pointed at the stub dir where no `.env` exists; the module cache makes everyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.env_file = REPO_ROOT / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# (env_file=".env", resolved against cwd — the dev-loop convenience noted inFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"the matching .env var"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# env_file=".env" would merge a developer's local .env (phantomFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# The stub YAML alone is not enough: Settings also merges a repo-root `.env`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Same isolation as above: never let the repo root's .env leak in.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.problems.append(f" {var} is not set (add it to .env)")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Usage (from the repo root, reusing Phase 1/2's existing config.yaml/.env):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""os.environ merged with the repo .env (env wins, matching the server)."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Desktop/Code launches spawn the server directly and do not read `.env`. DoFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Note: `.env` file support (via pydantic-settings' `env_file`) is a **localFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Isolate from the developer's repo-root .env: Settings has the dev-loopFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`.env` support is dev-loop convenience only — see module docstring.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""os.environ merged with the repo .env (env wins, matching the server)."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.dev-loop convenience only** — `uv run` inherits/reads `.env`, but real ClaudeFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file = REPO_ROOT / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.problems.append(f" {var} is not set (add it to .env)")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file = REPO_ROOT / ".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. 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.