mcp-context-pipe@0.5.10
VERIFIED· not startedPublisher claims: "Universal switchboard for the Context-Pipe Protocol (CPP)" 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
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-context-pipe` 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 (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-07 and scored it 81/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
"""Finds and loads a .env file from the current directory or parent directories into os.environ."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.dotenv_path = os.path.join(curr, ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.run([sift_exe, "--version"], capture_output=True, text=True, timeout=15)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.nodes = [{"cmd": "jq | rm -rf /", "args": []}]Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.dotenv_file = tmp_path / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.nodes = [{"cmd": "jq | rm -rf /", "args": []}]Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.nodes = json.dumps([{"cmd": "jq | rm -rf /"}])Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.found_paths.append(os.path.join(root, "AGENTS.md"))Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.nodes = json.dumps([{"cmd": "jq | rm -rf /"}])Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""load_dotenv_fallback loads .env variables into os.environ."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Use this at any agent-to-agent handoff boundary to prevent context flooding.\\n1. Identify the output text from Agent A and the name of Agent B that will consume it.\\n2. Call `pipe_agent_handoff(outFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.process = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# Create a dummy .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.outside_path = "/etc/passwd" if os.name != "nt" else "C:/Windows/System32/drivers/etc/hosts"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""When pipes.json does not exist, raw input must pass through unchanged."""Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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-context-pipe@0.5.10 as of 46 min ago. This is the package itself, not its dependencies.