mcp-trove-crunchtools@1.2.1
VERIFIED· not startedPublisher claims: "Self-hosted local file indexing MCP server with semantic search" 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
- It will ask for
GEMINI_API_KEYOPENAI_API_KEYConfiguration, not credentials: TROVE_BACKUP_DIR, TROVE_BACKUP_KEEP, TROVE_CHUNK_OVERLAP, TROVE_CHUNK_SIZE, TROVE_DB, TROVE_EMBED_THREADS, TROVE_EMBEDDING_MODEL, TROVE_EXCLUDE_PATTERNS, TROVE_INBOX_PATHS, TROVE_INDEX_LOCATION, TROVE_INDEX_OTHER, TROVE_INDEX_TYPES, TROVE_INDEX_WORKERS, TROVE_MANIFEST_DIR, TROVE_MAX_EXTRACT_TIMEOUTS, TROVE_MAX_TEXT_CHARS, TROVE_PATHS, TROVE_PDF_MAX_PAGES, TROVE_REQUIRE_MOUNT, TROVE_STATUS_FILE, TROVE_STATUS_FILE_MODE, TROVE_VISION_BACKEND, TROVE_VISION_FALLBACK_MODEL, TROVE_VISION_MAX_CALLS_PER_RUN, TROVE_VISION_MODEL, TROVE_VISION_PDF_SCANS, TROVE_VISION_PROMPT, TROVE_VISION_TIMEOUT- Where it talks to
- no vendor host named in the codeAlso openrouter.ai — 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 openrouter.ai as well as its own vendor. The guard injects GEMINI_API_KEY, OPENAI_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 (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 90/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
@pytest.mark.parametrize("escape", ["../../etc/passwd", "/etc/passwd", "..\\..\\secret.txt"])Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert sorted(Path(str(r["path"])).name for r in results) == [".env", "main.c"]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.db.insert_file(str(tmp_path / ".env"), "sum", "text", 1, MTIME)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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-trove-crunchtools@1.2.1 as of 4d ago. This is the package itself, not its dependencies.