scrape-n-search-mcp@0.1.1
VERIFIED· not startedPublisher claims: "MCP server unifying web-search and scraping providers behind a few agent tools" 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
EXA_API_KEYFIRECRAWL_API_KEYJINA_API_KEYSCRAPPEY_API_KEYSERPER_API_KEYTAVILY_API_KEYTINYFISH_API_KEYZENROWS_API_KEYConfiguration, not credentials: CACHE_TTL, DEFAULT_PROVIDER, ENABLED_TOOLS, HTTP_TIMEOUT, JINA_KEYLESS, PROVIDER_PRIORITY- Where it talks to
- no vendor host named in the codeAlso exa.ai, firecrawl.dev, jina.ai, scrappey.com, serper.dev, tavily.com, tinyfish.ai, zenrows.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 exa.ai, firecrawl.dev, jina.ai, scrappey.com, serper.dev, tavily.com, tinyfish.ai, zenrows.com as well as its own vendor. The guard injects EXA_API_KEY, FIRECRAWL_API_KEY, JINA_API_KEY, SCRAPPEY_API_KEY, SERPER_API_KEY, TAVILY_API_KEY, TINYFISH_API_KEY, ZENROWS_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-17 and scored it 83/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
# Load .env from the working directory (or its parents), then fall back toFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""--ask on a piped stdin (curl | bash) must degrade to 'declined', not crash."""Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.load_dotenv(PROJECT_DIR / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# the project's own .env. Existing environment variables take precedence andFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# .env regardless of the process working directory.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""--ask on a piped stdin (curl | bash) must degrade to 'declined', not crash."""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 scrape-n-search-mcp@0.1.1 as of 21 min ago. This is the package itself, not its dependencies.