mongreldb-viewer@1.6.7
VERIFIED· install onlyPublisher claims: "Desktop viewer and MCP server for MongrelDB" 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
MONGRELDB_VIEWER_PASSWORDMONGRELDB_VIEWER_TOKENor--auth-tokenConfiguration, not credentials: EXEC_PATH, MONGRELDB_VIEWER_PATH, MONGRELDB_VIEWER_SERVER, MONGRELDB_VIEWER_USER, REGEN_COMPAT_FIXTURE, TAURI_DEV_HOST, VITE_AUTO_OPEN_DB, WAYLAND_DISPLAY, XDG_CURRENT_DESKTOP- Where it talks to
- no vendor host named in the codeAlso visorcraft.com, webkitgtk.org, gtk.org, cairographics.org, libsoup.org, openssl.org, microsoft.com, webkit.org, vite.dev — 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 visorcraft.com, webkitgtk.org, gtk.org, cairographics.org, libsoup.org, openssl.org, microsoft.com, webkit.org, vite.dev as well as its own vendor. The guard injects MONGRELDB_VIEWER_PASSWORD, MONGRELDB_VIEWER_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 [email protected] 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-11 and scored it 88/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
subprocess.check_output(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.chmod 0644 "$desktop_file"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.let handle = mcp_server::start_http(executor, &host, port).await?;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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.