mcp-ui-explorer@0.1.20
VERIFIED· not startedPublisher claims: "An MCP server for exploring and interacting with UI elements" 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
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 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_UI_EXPLORER_UI_TARS__API_KEYConfiguration, not credentials: MCP_UI_EXPLORER_DEBUG, MCP_UI_EXPLORER_LOGGING__FORMAT, MCP_UI_EXPLORER_LOGGING__LEVEL, MCP_UI_EXPLORER_MEMORY__AUTO_SUMMARIZE, MCP_UI_EXPLORER_MEMORY__CONTEXT_THRESHOLD, MCP_UI_EXPLORER_UI__AUTO_VERIFY, MCP_UI_EXPLORER_UI__DEFAULT_VERIFICATION_TIMEOUT, MCP_UI_EXPLORER_UI__DEFAULT_WAIT_TIME, MCP_UI_EXPLORER_UI__SCREENSHOT_PREFIX, MCP_UI_EXPLORER_UI_TARS__API_URL, MCP_UI_EXPLORER_UI_TARS__ENABLE_FALLBACK, MCP_UI_EXPLORER_UI_TARS__MAX_RETRIES, MCP_UI_EXPLORER_UI_TARS__MODEL_NAME, MCP_UI_EXPLORER_UI_TARS__PROVIDER, MCP_UI_EXPLORER_UI_TARS__TIMEOUT, PYTHONIOENCODING- Where it talks to
- no vendor host named in the codeAlso azure.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 azure.com as well as its own vendor. The guard injects MCP_UI_EXPLORER_UI_TARS__API_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 (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 91/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 · 3 scenarios · 0 deviationsStatic findings
subprocess.call(('open' if sys.platform == 'darwin' else 'xdg-open', os.path.abspath(image_path)))Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.No other findings across 7,790 lines in 44 files.
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
No advisories in OSV for mcp-ui-explorer@0.1.20 as of 4d ago. This is the package itself, not its dependencies.