Mcp Recon Ng
Run recon-ng OSINT modules from your agent for authorized asset discovery, exposure checks, or competitive footprint research.
Overview
mcp-recon-ng is a MCP server for the Ship phase that exposes the recon-ng OSINT framework to coding agents over stdio for authorized reconnaissance workflows.
What is this MCP server?
- MCP server exposing the full recon-ng OSINT framework to agents
- PyPI package mcp-recon-ng version 0.1.0 with stdio transport
- Supports modular recon workflows instead of one-off manual CLI copy-paste
- GitHub: daedalus/mcp-recon-ng
- Requires ethical, authorized targets—framework-grade tooling not a casual scraper
- Server version 0.1.0
- PyPI identifier mcp-recon-ng
- Transport: stdio
What problem does it solve?
Running recon-ng module chains manually breaks agent momentum and invites mistakes on flags, workspaces, and reporting steps.
Who is it for?
Security-minded solo builders with explicit permission to test domains or gather competitive OSINT using recon-ng.
Skip if: Casual users seeking unauthorized scanning, spam enrichment, or a turnkey compliance certificate.
What do I get? / Deliverables
Your agent can drive recon-ng through MCP so repeatable OSINT and security recon sessions stay consistent and logged in your workflow.
- Agent-orchestrated recon-ng module sessions
- Structured OSINT outputs for security or competitor analysis notes
- Repeatable recon playbook executable from MCP clients
Recommended MCP Servers
Journey fit
How it compares
MCP bridge to recon-ng OSINT modules, not a curated threat-intel marketplace or a passive SEO keyword tool.
Common Questions / FAQ
Who is mcp-recon-ng for?
Developers and indie security testers who already use recon-ng and want agent-driven, authorized OSINT and recon module runs via MCP.
When should I use mcp-recon-ng?
Use it during Ship security hardening or authorized Idea-phase competitor research—not against systems you do not own or lack written permission to test.
How do I add mcp-recon-ng to my agent?
Install mcp-recon-ng from PyPI, configure stdio in your MCP client, install recon-ng and any module API keys locally, and define workspaces/targets before invoking tools.