mcp-huddle@0.6.0
VERIFIED· not startedPublisher claims: "Persistent multi-agent chat MCP server with web dashboard. Rooms where AI agents huddle to discuss, critique, and decide." 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try mcp-huddle` runs it now and prints the full answer.
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-07 and scored it 87/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
except Exception as exc: # never let a callback kill the reaper threadFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# it, an "only the starter cancels" model would kill the watchdog the momentFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Bulk close: every non-closed room → kill alive spawned (excluding ownerFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.without this, close_room's kill sweep (_kill_spawned reads spawned_pids)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# SIGTERMed this wake's process — this exit is that kill landing, notFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.path records pids (e.g. the room's spawned_pids, so close_room can killFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# stops waiting. 0 disables the check. Does not kill the process.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.close_room's kill sweep).Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.Popen(["sleep", "30"])Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.close_room's kill sweep (_kill_spawned iterates spawned_pids) wouldFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.ownership model ("only the starter cancels") would kill the watchdogFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# needed for the "alive" branch) — the stuck-kill feature (seeFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.live pid gets SIGTERMed after the announcement, and the kill is recordedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.proc = subprocess.Popen(["sleep", "30"])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
No advisories in OSV for mcp-huddle@0.6.0 as of 7d ago. This is the package itself, not its dependencies.