Test

Created By
nickpendinga year ago
Overview

What is mcp-recon?

mcp-recon is a conversational reconnaissance interface and MCP server that allows users to perform web domain reconnaissance using natural language commands. It integrates with AI interfaces to provide a seamless experience in HTTP infrastructure analysis.

How to use mcp-recon?

To use mcp-recon, you can interact with it through a compatible AI interface like Claude Desktop. Simply input your reconnaissance queries in natural language, and it will return the results based on the analysis mode you choose.

Key features of mcp-recon?

  • Conversational commands for easy execution of reconnaissance tasks.
  • Integration with Claude Desktop or other MCP-compatible tools.
  • Multiple analysis modes: lightweight and full reconnaissance.
  • Standalone ASN lookup for querying IPs and organizations.
  • Docker ready for secure and portable deployment.
  • Utilizes ProjectDiscovery's httpx for robust reconnaissance capabilities.

Use cases of mcp-recon?

  1. Performing quick HTTP status checks on websites.
  2. Conducting comprehensive metadata collection for security assessments.
  3. Looking up ASN information for IP addresses.

FAQ from mcp-recon?

  • Can mcp-recon perform reconnaissance on any domain?

Yes, as long as you have permission to scan the domain.

  • Is mcp-recon easy to set up?

Yes, it can be easily set up using Docker and requires minimal configuration.

  • What is the Model Context Protocol (MCP)?

MCP is an open standard that allows AI assistants to interact with external tools and systems, facilitating efficient workflows.

Server Config

{
  "mcpServers": {
    "歌者PPT": {
      "command": "npx",
      "args": [
        "-y",
        "gezhe-mcp-server@latest"
      ],
      "env": {
        "API_KEY": "替换为获取的 API_KEY"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nickpending
Star
-
Language
-
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)

9 hours ago
Alloy

2 days ago