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.
npx agentmods add mcp/nickjlucker/mcp-greynoise/greynoisegit clone --depth 1 https://github.com/nickjlucker/mcp-greynoiseWrote 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/nickjlucker/mcp-greynoise/greynoise)<a href="https://agentmods.dev/mcp/nickjlucker/mcp-greynoise/greynoise"><img src="https://agentmods.dev/badge/mcp/nickjlucker/mcp-greynoise/greynoise.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
greynoise 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 5d 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
{ "greynoise": { "command": "npx", "args": [ "-y", "mcp-greynoise" ], "env": { "GREYNOISE_API_KEY": "" } } }
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.
- 5d ago First seen · 12 lines scan A d91731377d25
greynoise is an MCP server published in the GitHub repository nickjlucker/mcp-greynoise (0 stars, last pushed 6mo 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
greynoise
GreyNoise Community MCP — internet scanner classification (free tier with key). Remote server at gateway.pipeworx.io.
data-breach-detector
Read-only breach-intelligence MCP: reports THAT an organization was breached and which data types leaked, across full history from public feeds (HaveIBeenPwned, RansomLook, ransomwatch archive, SEC 8-K 1.05). Never the leaked data. Runs locally from the data-breach-detector Python package.
data
Mocap, rehab biomechanics, threat intel, fleet vision. 21 MCP tools, 10 free. x402/USDC paid. Remote server at api.rtkmotion.io.
nullcone
Real-time threat intel for AI agents: 890K+ IOCs incl. prompt-injection & AI-skill threats. Remote server at nullcone.ai.
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.