Skills/PyPI/serp-api-mcp

serp-api-mcp@0.1.1

VERIFIED· not started

Publisher claims: "MCP server for Google search using SERPAPI" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher lukelanterme · publishing for 504 daysInstalls 62Last detonated 1 h ago
$claude mcp add serp-api-mcp -- uvx serp-api-mcp
WatchReport an issue

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
SERPAPI_API_KEYSERPAPI_KEYConfiguration, not credentials: MAX_RETRIES, MCP_CONNECTION_TYPE, MCP_PORT, REQUEST_TIMEOUT
Where it talks to
serpapi.com (its own)
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. It asks for SERPAPI_API_KEY, SERPAPI_KEY and talks to serpapi.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets SERPAPI_API_KEY=serpapi.com,SERPAPI_KEY=serpapi.com -- uvx serp-api-mcp

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-18 and scored it 86/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 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocesssecond launch, clock +45 days, CI unset

Static findings

HIGH
Access to sensitive file pathsCLAUDE.md:140 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsCLAUDE.md:15 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- Place all sensitive information in a .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsCLAUDE.md:145 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesCreate a `.env` file with: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 pathsCLAUDE.md:141 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Edit .env and add your SERPAPI_API_KEYFix: 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
≈2,019 tok
2 files · 21 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 serp-api-mcp@0.1.1 as of 29 min ago. This is the package itself, not its dependencies.