Skills/npm/mcp-shodan

mcp-shodan@1.0.41

VERIFIED

Publisher claims: "A Model Context Protocol server for Shodan API queries." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher burtthecoder · publishing for 707 daysInstalls 4,458Last detonated 10 h ago
$claude mcp add mcp-shodan -- npx -y @burtthecoder/mcp-shodan
WatchReport an issue

Coverage

Started with a decoy SHODAN_API_KEY; tool list observed. Tool calls with a real credential not tested.
Tested
server startup with a tagged decoy in SHODAN_API_KEY · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with a real credential
Needs
SHODAN_API_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

Before you give it your token

It will ask for
SHODAN_API_KEYConfiguration, not credentials: MCP_ENDPOINT, MCP_HOST, MCP_PORT, MCP_TRANSPORT
Where it talks to
no vendor host named in the codeAlso shodan.io — 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 a real credential

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names shodan.io as well as its own vendor. The guard injects SHODAN_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @burtthecoder/mcp-shodan

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

What changed since 1.0.37

vet-skills diff mcp-shodan 1.0.37 1.0.41

In the sandbox, this version reached for nothing 1.0.37 did not. Compared from the two recorded runs, not from source.

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 93/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 · 48 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.8sprocessdependency install exit 0
28sprocessrelaunched with a decoy SHODAN_API_KEY (tagged; nothing real)
48sclaimed11 tools with a decoy SHODAN_API_KEY: ip_lookup, shodan_search, cve_lookup, dns_lookup, reverse_dns_lookup, cpe_lookup, cves_by_product, shodan_count, domain_info, api_info, search_filters
48stools48f501e746d44e98
48stoolsf230c13681166c1a
48stoolsdd1df31178cadd6d
48stoolsddf2adc5c79ffef0
48stools4e13f523ed1488da
48stools2b66c3819dcabca7
48stoolsfafcec08357de5f1
48stools491d5e195d7f0f84
48stools21d3679c8a725ded
48stools9c8a7be2fe691c28
48stools7e169ca28f7183b7
48sprocessscript backend runs setup only
48sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandpackage.json:12 · File permission modification command — agent changes file ownership/permissions"build": "tsc && chmod +x build/index.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

No other findings across 1,209 lines in 18 files.

Cost to the agent

Instructions loaded
≈53 tok
1 file · 18 in bundle
Tool list per prompt
≈2,245 tok
11 tools · 204 per tool
Handshake
615 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 239

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 @burtthecoder/mcp-shodan@1.0.41 as of 10 h ago. This is the package itself, not its dependencies.