Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/blisspixel/reconInstalling this writes the configuration, not the program: `recon` has to be on your PATH already, or the server will not start.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/blisspixel/recon/claude-code-recon)<a href="https://agentmods.dev/mcp/blisspixel/recon/claude-code-recon"><img src="https://agentmods.dev/badge/mcp/blisspixel/recon/claude-code-recon/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/blisspixel/recon/claude-code-recon"><img src="https://agentmods.dev/badge/mcp/blisspixel/recon/claude-code-recon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
recon scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"recon": {
"command": "recon",
"args": [
"mcp"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 8 lines scan A 22f02f4de1ed
recon is an MCP server published in the GitHub repository blisspixel/recon (5 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
recon
MCP server "recon" as configured in nekiyRichie/recon-mcp. Launched with /absolute/path/to/recon-mcp/.venv/bin/recon-mcp. Needs 1 environment variable to run.
mcp
Real-time global intelligence across conflict, markets, energy, trade, shipping and cyber. 95 tools. Remote server at worldmonitor.app.
openosint
AI-powered OSINT agent, MCP server, and CLI. Interactive REPL + 19 tools. Anthropic Claude or local Ollama. For authorized security research use only. Runs locally from the openosint Python package. Needs 5 environment variables to run.
shodan
MCP server for Shodan API — device search, IP and domain recon, DNS, and CVE/CPE queries. Runs locally from the @burtthecoder/mcp-shodan npm package. Needs 1 environment variable to run.
api
31 tools: CVE (340K+ EPSS/KEV), OSINT, threat intel, dep audit, code sec. No API key needed. Remote server at api.contrastcyber.com.
mcp-vanguard
MCP server "mcp-vanguard" as configured in skyvanguard/mcp-vanguard. Runs locally from the mcp-vanguard npm package.