Shodan MCP Server

Created By
Cyreslab-AIa year ago
A Model Context Protocol server that provides access to Shodan API functionality
Overview

what is Shodan MCP Server?

Shodan MCP Server is a Model Context Protocol server that provides access to Shodan API functionality, enabling AI assistants to query information about internet-connected devices and services, thereby enhancing cybersecurity research and threat intelligence capabilities.

how to use Shodan MCP Server?

To use the Shodan MCP Server, clone the repository, install dependencies, build the project, and configure your Shodan API key. Then, integrate it with your MCP-compatible assistants.

key features of Shodan MCP Server?

  • Host Information Lookup: Retrieve detailed information about specific IP addresses.
  • Search Functionality: Search Shodan's database for devices and services using various filters.
  • Vulnerability Information: Access details about specific CVE vulnerabilities.
  • Result Summarization: Generate concise summaries of search results.
  • Response Sampling: Limit response size to reduce token usage.
  • Field Selection: Filter results to include only specific fields.

use cases of Shodan MCP Server?

  1. Conducting cybersecurity research by analyzing internet-connected devices.
  2. Identifying vulnerabilities in devices and services for threat intelligence.
  3. Enhancing AI assistants' capabilities to provide real-time data on internet devices.

FAQ from Shodan MCP Server?

  • Can I use Shodan MCP Server for any type of device?

Yes! It can be used to query information about a wide range of internet-connected devices.

  • Is there a cost associated with using the Shodan API?

The Shodan API may have usage limits and costs depending on the plan you choose.

  • How do I report issues or suggest features?

You can open an issue on the GitHub repository or contact the developers directly.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Cyreslab-AI
Star
1
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago