mcp-shodan@1.0.41
VERIFIEDPublisher claims: "A Model Context Protocol server for Shodan API queries." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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.
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.41In 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 deviationsStatic findings
"build": "tsc && chmod +x build/index.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.No other findings across 1,209 lines in 18 files.
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 @burtthecoder/mcp-shodan@1.0.41 as of 10 h ago. This is the package itself, not its dependencies.