Greynoise

io.github.nickjlucker由 GitHub 帳號 nickjlucker 發布v0.1.0更新於 Oct 24, 2026

MCP server for GreyNoise API - Check if IPs are internet background noise or targeted attacks

概覽

AI 產生的概覽

一個本機 MCP 伺服器,透過查詢 GreyNoise API,讓助理判斷 IP 位址是網際網路背景掃描雜訊、已知良性服務,還是可能針對性的攻擊流量。

可以做什麼
查詢單一 IPv4 位址在 GreyNoise 中的雜訊、RIOT 與分類結果,並給出對安全研判的含義解讀。一次呼叫最多查詢十個 IPv4 位址,回傳合併的結果清單與圖例。以資源形式讀取 GreyNoise API 狀態與速率限制資訊。
適用情境
適合在 SOC 告警研判、事件應變、威脅狩獵或日誌分析時使用,判斷日誌中的可疑 IP 是背景掃描器、已知良性服務,還是可能專門針對你的流量。
執行需求
透過 npx 或全域 npm 安裝作為本機程序執行,需要 Node.js。每天約 10 次查詢無需 API 金鑰;設定 GREYNOISE_API_KEY 環境變數後,免費層可提升到每天 50 次。需要能存取 GreyNoise API 的網路。
安裝前請注意
選用的 GREYNOISE_API_KEY 屬於機密,不應提交到程式庫或被記錄。查詢內容會傳送給 GreyNoise,且速率限制與 GreyNoise Visualizer 共用。此伺服器聲明為唯讀,除目前請求外不儲存資料。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Greynoise,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

mcp-greynoise

[npm version] [License: MIT]

MCP server for the GreyNoise API — check if IP addresses are internet background noise or potentially targeted attacks.

Quick Start

bash
npx mcp-greynoise

That's it. Works out of the box with 10 lookups/day (no API key needed).

What is GreyNoise?

GreyNoise collects and analyzes internet-wide scan traffic. It tells you:

  • Noise: Is this IP mass-scanning the internet? (botnets, researchers, crawlers)
  • RIOT: Is this IP a known benign service? (Google, Cloudflare, Microsoft, etc.)
  • Classification: Malicious, benign, or unknown

Why this matters for security

When you see suspicious traffic in your logs:

GreyNoise ResultInterpretation
NOISE + MaliciousBackground attack traffic (scanners, botnets) — likely untargeted
NOISE + BenignSecurity researchers, search crawlers — usually safe
RIOTKnown good service (CDN, DNS, cloud) — almost certainly benign
NOT NOISE⚠️ This IP is NOT mass-scanning — traffic may be targeted at you

The "NOT NOISE" case is often the most important — it suggests someone is specifically interested in your systems.

Demo

Example output from check_ip:

IP: 51.91.185.74Classification: MALICIOUSNoise: YES - This IP has been observed scanning the internetRIOT: NO - Not a known benign service IPLast Seen: 2024-01-15Details: https://viz.greynoise.io/ip/51.91.185.74
--- Interpretation ---🚨 This IP is actively scanning the internet and classified as MALICIOUS.    Likely a scanner, botnet, or threat actor.

Installation

npm (recommended)

bash
npm install -g mcp-greynoise

npx (no install)

bash
npx mcp-greynoise

From source

bash
git clone https://github.com/nickjlucker/mcp-greynoise.gitcd mcp-greynoisenpm installnpm run buildnode build/index.js

Configuration

Claude Desktop

Add to your claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

json
{  "mcpServers": {    "greynoise": {      "command": "npx",      "args": ["mcp-greynoise"],      "env": {        "GREYNOISE_API_KEY": "your-api-key-here"      }    }  }}

Environment Variables

VariableRequiredDescription
GREYNOISE_API_KEYNoAPI key for higher rate limits (50/day vs 10/day)

Get a free API key at viz.greynoise.io/signup.

⚠️ Never commit API keys. See .env.example for the recommended setup.

Tools

check_ip

Check a single IP address against GreyNoise.

Input:

  • ip (string): IPv4 address to check

check_ips

Check multiple IP addresses in one call (max 10).

Input:

  • ips (string[]): Array of IPv4 addresses

Example output:

=== Results ===8.8.8.8: RIOT (benign service) [Google]51.91.185.74: NOISE - MALICIOUS192.168.1.1: NOT NOISE (potentially targeted)
--- Legend ---RIOT: Known benign service (CDN, DNS, etc.)NOISE: IP is mass-scanning the internetNOT NOISE: IP is NOT mass-scanning (traffic may be targeted)

Resources

greynoise://status

Returns API status and rate limit information.

Rate Limits

TierDaily Lookups
Unauthenticated10
Free account50
Paid plansHigher

Rate limits are shared between API calls and the GreyNoise Visualizer.

Security

This server:

  • Only reads from the GreyNoise API (no scanning, no exploitation)
  • Does not store any data beyond the current request
  • Does not transmit your API key anywhere except to GreyNoise
  • Performs reputation/telemetry enrichment only

Your API key is passed via environment variable and never logged.

Use Cases

  • SOC Triage: Quickly determine if alert IPs are background noise or targeted
  • Incident Response: Identify if attacker IPs are mass-scanners or focused threats
  • Threat Hunting: Find IPs in your logs that aren't mass-scanners (potentially targeted)
  • Log Analysis: Reduce false positives by filtering out known scanners

Development

bash
# Install dependenciesnpm install
# Run in development modenpm run dev
# Build for productionnpm run build
# Run built versionnpm start

License

MIT

Links

來源:README.md,提交 6aa46ac

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分