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/Gentle-bae/dns-eyesWrote 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/gentle-bae/dns-eyes/dns-eye)<a href="https://agentmods.dev/mcp/gentle-bae/dns-eyes/dns-eye"><img src="https://agentmods.dev/badge/mcp/gentle-bae/dns-eyes/dns-eye/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/gentle-bae/dns-eyes/dns-eye"><img src="https://agentmods.dev/badge/mcp/gentle-bae/dns-eyes/dns-eye.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dns-eye 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
{ "dns-eye": { "command": "uvx", "args": [ "dns-eye" ] } }
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 · 8 lines scan A f245177d6ca1
dns-eye is an MCP server published in the GitHub repository Gentle-bae/dns-eyes (0 stars, last pushed 25d 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
attack-surface-mcp-server
Passive external attack-surface mapping: CT subdomains, DNS, TLS, HTTP posture, RDAP/WHOIS, Shodan. Runs locally from the @cyanheads/attack-surface-mcp-server npm package. Needs 8 environment variables to run.
mcp
Live markets, conflicts, country risk, chokepoints, energy, and China decision signals. 72 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.
dns-aid
DNS-based Agent Identification and Discovery - Reference Implementation. Runs locally from the dns-aid Python package. Needs 1 environment variable to run.
pihole-mcp
MCP server "pihole-mcp" as configured in hexamatic/pihole-mcp. Runs in Docker (ghcr.io/hexamatic/pihole-mcp:0.8.1). Needs 7 environment variables to run.
recon
MCP server "recon" as configured in blisspixel/recon. Launched with recon mcp.