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/nekiyRichie/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/nekiyrichie/recon-mcp/recon)<a href="https://agentmods.dev/mcp/nekiyrichie/recon-mcp/recon"><img src="https://agentmods.dev/badge/mcp/nekiyrichie/recon-mcp/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/nekiyrichie/recon-mcp/recon"><img src="https://agentmods.dev/badge/mcp/nekiyrichie/recon-mcp/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 10d 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": "/absolute/path/to/recon-mcp/.venv/bin/recon-mcp",
"env": {
"RECON_MCP_LOG": "WARNING"
}
}
}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.
- 10d ago First seen · 8 lines scan A 006b3ec42936
recon is an MCP server published in the GitHub repository nekiyRichie/recon-mcp (0 stars, last pushed 1mo ago), 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
recon
MCP server "recon" as configured in blisspixel/recon. Launched with recon mcp.
mcp-threatintel
Unified threat intel - OTX, AbuseIPDB, GreyNoise, abuse.ch, Feodo Tracker. Runs locally from the mcp-threatintel-server npm package. Needs 4 environment variables to run.
erlik-graph
MCP server "erlik-graph" as configured in malkreide/erlik-graph. Runs erlik_graph.adapters.mcp_server with python. Needs 6 environment variables to run.
urlscan-mcp
MCP server "urlscan-mcp" as configured in Moussa93x/urlscan-mcp. Runs locally from the urlscan-mcp Python package.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
godot-mcp
MCP server for full Godot 4.x engine control with 165 tools for AI-driven game development. Runs locally from the @tugcantopaloglu/godot-mcp npm package.