Skills/npm/search1api-mcp

search1api-mcp@0.13.0

VERIFIED

Publisher 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.

Registry npm (MCP server)Publisher superagents-lab · publishing for 724 daysInstalls 4,200Last detonated 6 h ago
$claude mcp add search1api-mcp -- npx -y search1api-mcp
WatchReport an issue

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 we saw when it ran
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.

$vet-skills run --secrets API_KEY=search1api.com,OAUTH_AUTHORIZATION_SERVER=search1api.com,SEARCH1API_KEY=search1api.com -- npx -y search1api-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 0.12.0

vet-skills diff search1api-mcp 0.12.0 0.13.0

This version reaches for something 0.12.0 did not: 1 new tool (query_dataset). Compared from the two recorded runs, not from source.

New tools
query_dataset

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-19 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 · 25 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
5.0sprocessdependency install exit 0
25sclaimed11 tools: search, news, crawl, sitemap, trending, ask, maps, query_dataset, deepcrawl, render_results, send_feedback
25stoolsa4e6d3f98109c8e1
25stools6b1855a51f03d674
25stools792a67a0285c543f
25stoolsb4f8bc3652ed0db7
25stools7078e2ccdbed2f42
25stoolsb8234870dd9caeb6
25stools3708dcafc185c2d2
25stools67fcd75a53cec02a
25stoolsbd637f11edf63057
25stools8eeac134ce066d85
25stools625c3e9b050594a9
25sprocessscript backend runs setup only
25sprocessno install scripts to re-run

Static findings

HIGH
Credential pass-through configurationbuild/api.js:38 · Credential pass-through configuration — agent relays sensitive credentialsthrow 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.
AST02
HIGH
Access to sensitive file pathsbuild/config.js:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslog('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.
AST05
HIGH
Access to sensitive file pathsbuild/config.js:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// 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.
AST05
HIGH
Access to sensitive file pathsbuild/config.js:15 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslog(`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.
AST05
HIGH
Access to sensitive file pathsbuild/config.js:14 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst projectRootEnvPath = join(__dirname, '../.env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsbuild/config.js:18 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslog(`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.
AST05

Cost to the agent

Instructions loaded
≈62 tok
1 file · 37 in bundle
Tool list per prompt
≈3,444 tok
11 tools · 313 per tool
Handshake
1076 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 397

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.13.0 as of 6 h ago. This is the package itself, not its dependencies.