rf-mcp@0.36.0
VERIFIED· not startedPublisher claims: "Robot Framework MCP Server - Natural Language Test Automation Bridge" 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
MCP_TOKENROBOTMCP_ATTACH_TOKENROBOTMCP_FRONTEND_SECRET_KEYConfiguration, not credentials: CODEX_HOME, CONDA_PREFIX, ROBOTMCP_API_GUIDANCE, ROBOTMCP_ATTACH_DEFAULT, ROBOTMCP_ATTACH_HOST, ROBOTMCP_ATTACH_PORT, ROBOTMCP_ATTACH_STRICT, ROBOTMCP_BRIDGE_HEARTBEAT, ROBOTMCP_CATALOG_HARD_CAP, ROBOTMCP_FRONTEND_ALLOWED_HOSTS, ROBOTMCP_FRONTEND_BASE_PATH, ROBOTMCP_FRONTEND_DB, ROBOTMCP_FRONTEND_DEBUG, ROBOTMCP_FRONTEND_EVENT_BUFFER, ROBOTMCP_FRONTEND_HOST, ROBOTMCP_FRONTEND_PORT, ROBOTMCP_FRONTEND_STATIC_ROOT, ROBOTMCP_FRONTEND_TIME_ZONE, ROBOTMCP_HEARTBEAT_INTERVAL, ROBOTMCP_HEARTBEAT_THRESHOLD, ROBOTMCP_INSTRUCTION_MODE, ROBOTMCP_LAZY_INIT, ROBOTMCP_LIBRARY_DETECTION_AMBIGUITY_WINDOW, ROBOTMCP_LIBRARY_DETECTION_CONFLICT_THRESHOLD, ROBOTMCP_LIBRARY_DETECTION_MIN_SCORE, ROBOTMCP_LOG_LEVEL, ROBOTMCP_MCP_LOG_NOTIFICATIONS, ROBOTMCP_MODEL_TIER, ROBOTMCP_PLUGIN_PATHS, ROBOTMCP_SCREENSHOT_DIR, ROBOTMCP_SCREENSHOT_MODE, ROBOTMCP_STARTUP_CLEANUP, ROBOTMCP_TOOL_PROFILE, ROBOTMCP_USE_SAMPLING, ROBOTMCP_WARMUP, XDG_STATE_HOME- Where it talks to
- no vendor host named in the codeAlso robotframework.org, herokuapp.com, unpkg.com, jsdelivr.net, slow-website.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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names robotframework.org, herokuapp.com, unpkg.com, jsdelivr.net, slow-website.com as well as its own vendor. The guard injects MCP_TOKEN, ROBOTMCP_ATTACH_TOKEN, ROBOTMCP_FRONTEND_SECRET_KEY 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 [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 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
r = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run([*interp, "-c", f"import {lib}"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run(argv + ["init"], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run([Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.<summary>Legacy / manual config (running from a checkout, HTTP transport)</summary> ```json { "servers": { "robotmcp": { "type": "stdio", "command": "uv", "argsFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.r = subprocess.run(probe, capture_output=True, text=True, timeout=timeout,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."AUTH TOKEN: capture the token from ${resp.json()[\"token\"]}, then send "Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.p = subprocess.Popen(argv, stdin=subprocess.PIPE, stdout=subprocess.PIPE,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run(["uv", "pip", "install", "--python", str(env.python), spec],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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.