Evaluation report

• Repository is reachable

  https://github.com/w0h1v/mcp-shodan @ 59c70b9 — ★ 139 · TypeScript · MIT · last push 3 months ago

• Manifest detected

  kind=mcp slug=burtthecoder-mcp-shodan · source=package.json

• Slug is URL-safe

  "burtthecoder-mcp-shodan" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/burtthecoder-mcp-shodan

• Version is semver

  1.0.27

• Description quality

  9 words · 55 chars — OK but more detail helps

• README is present and substantial

  10,080 chars · 11 sections · 10 code blocks

• Tags / topics declared

  24 total — mcp, shodan, mcp-shodan, cybersecurity, agents, network-reconnaissance (+18)

• README has usage / example sections

  found: Quick Start

• Homepage / docs URL declared

  https://github.com/BurtTheCoder/mcp-shodan#readme

• Dependencies: known vulnerabilitieswarn

  14 high/critical advisories — [email protected] (HIGH: GHSA-35jp-ww65-95wh) · [email protected] (HIGH: GHSA-3g43-6gmg-66jw) (+12)

  Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)

• LICENSE file at repo root

  LICENSE

• No sensitive files in the repo

  scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found

• MCP: @modelcontextprotocol/sdk in dependencieswarn

  No @modelcontextprotocol/sdk dependency declared

  Run `npm i @modelcontextprotocol/sdk` so consumers can audit your stack.

• MCP: launch path

  bin: mcp-shodan

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Tests detectedwarn

  no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files

  Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.

• Recent activity

  last push 3 months ago

• CI configuration detected

  GitHub Actions (1 workflows)

This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.