search-fusion-mcp@3.0.5
VERIFIED· not startedPublisher claims: "🔍 High-Availability Multi-Engine Search Aggregation MCP Server with Enhanced Proxy Auto-Detection" 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
- It will ask for
BAIDU_API_KEYBAIDU_SEARCH_API_KEYBAIDU_SEARCH_SECRET_KEYBAIDU_SECRET_KEYBING_API_KEYBING_SEARCH_API_KEYEXA_API_KEYEXA_SEARCH_API_KEYGOOGLE_API_KEYGOOGLE_SEARCH_API_KEYJINA_API_KEYJINA_SEARCH_API_KEYSERPER_API_KEYSERPER_SEARCH_API_KEYConfiguration, not credentials: ALL_PROXY, GOOGLE_CSE_ID, GOOGLE_SEARCH_CSE_ID, LOG_FILE, LOG_ROTATION- Where it talks to
- no vendor host named in the codeAlso jina.ai, serper.dev, microsoft.com, archive.org — 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 jina.ai, serper.dev, microsoft.com, archive.org as well as its own vendor. The guard injects BAIDU_API_KEY, BAIDU_SEARCH_API_KEY, BAIDU_SEARCH_SECRET_KEY, BAIDU_SECRET_KEY, BING_API_KEY, BING_SEARCH_API_KEY, EXA_API_KEY, EXA_SEARCH_API_KEY, GOOGLE_API_KEY, GOOGLE_SEARCH_API_KEY, JINA_API_KEY, JINA_SEARCH_API_KEY, SERPER_API_KEY, SERPER_SEARCH_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 (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-17 and scored it 91/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
result = subprocess.run([Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run([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 search-fusion-mcp@3.0.5 as of 21 min ago. This is the package itself, not its dependencies.