realtimex-web-search-mcp-server@0.1.0
VERIFIED· not startedPublisher claims: "MCP server for web search operations - provides utility tools for performing web searches via APIs with multiple provider support" 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
BING_SEARCH_API_KEYGOOGLE_SEARCH_API_KEYSERPAPI_API_KEYSERPER_API_KEYSERPLY_API_KEYTAVILY_API_KEYConfiguration, not credentials: BING_SEARCH_MAX_RETRIES, BING_SEARCH_TIMEOUT, DUCKDUCKGO_MAX_RETRIES, DUCKDUCKGO_TIMEOUT, GOOGLE_CSE_ID, GOOGLE_SEARCH_MAX_RETRIES, GOOGLE_SEARCH_TIMEOUT, SEARXNG_BASE_URL, SEARXNG_MAX_RETRIES, SEARXNG_TIMEOUT, SERPAPI_MAX_RETRIES, SERPAPI_TIMEOUT, SERPER_MAX_RETRIES, SERPER_TIMEOUT, SERPLY_MAX_RETRIES, SERPLY_TIMEOUT, TAVILY_MAX_RETRIES, TAVILY_TIMEOUT, WEB_SEARCH_DEFAULT_MAX_RESULTS, WEB_SEARCH_DEFAULT_PROVIDER, WEB_SEARCH_DEFAULT_TIMEOUT, WEB_SEARCH_ENABLE_FALLBACKS, WEB_SEARCH_SERVER_NAME, WEB_SEARCH_SERVER_VERSION- Where it talks to
- no vendor host named in the codeAlso google.com, microsoft.com, duckduckgo.com, searxng.org, serper.dev, serply.io, tavily.com, your-searxng-instance.com, searx.be, sapti.me, tiekoetter.com — 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 google.com, microsoft.com, duckduckgo.com, searxng.org, serper.dev, serply.io, tavily.com, your-searxng-instance.com, searx.be, sapti.me, tiekoetter.com as well as its own vendor. The guard injects BING_SEARCH_API_KEY, GOOGLE_SEARCH_API_KEY, SERPAPI_API_KEY, SERPER_API_KEY, SERPLY_API_KEY, TAVILY_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-15 and scored it 95/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
No findings across 11,200 lines in 33 files.
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 realtimex-web-search-mcp-server@0.1.0 as of 1 h ago. This is the package itself, not its dependencies.