mcp-codebase-searcher@0.2.14
VERIFIED· install onlyPublisher claims: "A Python tool to scan codebases, search for text/regex patterns, and elaborate on findings using AI models via LiteLLM." 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
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
- use of the skill by an agent
Not enough was observed to say yet. Nothing executable in the bundle ran; the trace covers the install step only. 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-codebase-searcher` 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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-07 and scored it 85/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
from dotenv import load_dotenv # Added for explicit .env loadingFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Loads the Google API key, trying .env first, then environment variables.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Prints a warning if .env is used but the key isn't in it or if not found at all.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# print(f"DEBUG: [config.py] Expected .env path: {dotenv_path}", file=sys.stderr)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.dotenv_path = os.path.join(os.getcwd(), '.env')Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# print(f"DEBUG: [config.py] .env file found at {dotenv_path}", file=sys.stderr)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# This explicitly loads .env here, overriding any system env var if key is present in .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load .env from current working directory to check for GOOGLE_API_KEYFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# but this ensures CLI-level .env takes precedence if no direct arg or config file key.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Ensure we try to load .env variables locally for litellm settings."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.self.assertIn("Match in: file1.txt", output)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.**Rule 2: The LLM should be instructed to use absolute paths.**Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.dotenv_path = os.path.join(os.getcwd(), '.env')Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.self.assertIn("Match in: file1.txt", output)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.self.assertIn("## File: `file1.txt`", output)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.**Rule 1: Always use FULL absolute paths for your executable command.**Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.self.assertIn("## File: `file1.txt`", output)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. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for mcp-codebase-searcher@0.2.14 as of 2 h ago. This is the package itself, not its dependencies.