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/nan786521/recon-mcpWrote 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/nan786521/recon-mcp/recon-kit-mcp)<a href="https://agentmods.dev/mcp/nan786521/recon-mcp/recon-kit-mcp"><img src="https://agentmods.dev/badge/mcp/nan786521/recon-mcp/recon-kit-mcp/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/nan786521/recon-mcp/recon-kit-mcp"><img src="https://agentmods.dev/badge/mcp/nan786521/recon-mcp/recon-kit-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
recon-kit-mcp 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 9d 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-kit-mcp": {
"command": "uvx",
"args": [
"recon-kit-mcp"
],
"env": {}
}
}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.
- 9d ago First seen · 9 lines scan A 8ecde28ba186
recon-kit-mcp is an MCP server published in the GitHub repository nan786521/recon-mcp (1 stars, last pushed yesterday), licensed MIT. 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
domain-intel-mcp
Domain & company intel for AI agents: RDAP, DNS, email deliverability, tech stack. No API keys. Remote server at domain.datakoot.com.
pg-context-mcp
MCP server "pg-context-mcp" as configured in mewsyy/pg-context. Runs locally from the pg-context-mcp npm package.
broke2built-skills-mcp
29 live data skills for agents: email/DNS/domain intel, web audits, EVM reads. Free tier. Runs locally from the broke2built-skills-mcp npm package. Needs 1 environment variable to run.
ovh-api-mcp
MCP server "ovh-api-mcp" as configured in davidlandais/ovh-api-mcp. Runs in Docker (ghcr.io/davidlandais/ovh-api-mcp:0.3.0). Needs 7 environment variables to run.
midos
MCP Community Library — Curated knowledge, skill packs, and semantic search for AI coding agents. Runs locally from the midos-mcp Python package. Needs 1 environment variable to run.
netops-mcp
Local-first network diagnostics & tunnel/proxy MCP server. Diagnose connectivity and inspect your WireGuard/proxy setup from your AI assistant — from your own machine, not a remote probe. Runs locally from the netops-mcp npm package.