An MCP server configuration for recon, a tool that gathers information about internet domains and their related services. MCP lets an AI coding assistant call such external tools.

Use it when configuring a local recon integration for domain-information and DNS-related investigations.

It supplies the command needed to start recon locally and make its functions available to the assistant.

recon — MCP server by blisspixel

Install

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.

agentmods

npx agentmods add mcp/blisspixel/recon/claude-code-recon

Clone the repo

git clone --depth 1 https://github.com/blisspixel/recon

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Or install recon, the plugin that ships this one along with the rest of its 1 MCP server.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

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 3d 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.

agents/claude-code/.mcp.json · 8 lines

What it actually says

{
  "recon": {
    "command": "recon",
    "args": [
      "mcp"
    ]
  }
}

Changes

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.

3d ago First seen · 8 lines scan A 22f02f4de1ed

Subscribe to this mod's changes

recon is an MCP server published in the GitHub repository blisspixel/recon (4 stars, last pushed 3d ago), 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.

Research domain-intelligence email-security mcp osint passive-recon recon

recon

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

recon

mcp

openosint

api

mcp-threatintel

proofpoint-mcp