search1api-mcp@0.12.0
VERIFIEDPublisher claims: "A Model Context Protocol (MCP) server that provides search and crawl functionality using Search1API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Server started and answered tools/list.- Tested
- MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with real credentials
Before you give it your token
- It will ask for
API_KEYOAUTH_AUTHORIZATION_SERVERSEARCH1API_KEYConfiguration, not credentials: MCP_ALLOWED_HOSTS, MCP_ALLOWED_ORIGINS, SEARCH1API_API_URL, SEARCH1API_UI_DOMAIN, SERVER_ICON_PATH- Where it talks to
- search1api.com, s1.dev (its own)Also claude.ai, duckduckgo.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
- what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names claude.ai, duckduckgo.com as well as its own vendor. The guard injects API_KEY, OAUTH_AUTHORIZATION_SERVER, SEARCH1API_KEY only into requests to search1api.com (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) on 2026-11-14 and scored it 84/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 26 s · 2 scenarios · 0 deviationsStatic findings
// If not found in env, try loading from .env file in project root as fallbackFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.throw new Error("API key is required. Provide SEARCH1API_KEY or pass apiKey explicitly.");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.log('SEARCH1API_KEY not found in environment, attempting to load from .env file in project root...');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.log(`Failed to load .env from ${projectRootEnvPath}: ${result.error.message}`);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.log(`Attempting to load .env from: ${projectRootEnvPath}`);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const projectRootEnvPath = join(__dirname, '../.env');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 search1api-mcp@0.12.0 as of 10 h ago. This is the package itself, not its dependencies.