Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.nickjlucker/greynoise

NPM · MCP-GREYNOISE · SCANNED AUG 3

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

Available components

npm · mcp-greynoise 70
+17 this week 70 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 185 tokens (~61/item across 3 items; 2 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · mcp-greynoise

# add to Claude Code
claude mcp add nickjlucker-greynoise -- npx -y mcp-greynoise
# add to Codex CLI
codex mcp add nickjlucker-greynoise -- npx -y mcp-greynoise
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nickjlucker-greynoise": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-greynoise"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nickjlucker-greynoise --command npx --arg -y --arg mcp-greynoise
# ~/.hermes/config.yaml
mcp_servers:
  nickjlucker-greynoise:
    command: "npx"
    args: ["-y", "mcp-greynoise"]
// mcp.json
{
  "mcpServers": {
    "nickjlucker-greynoise": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-greynoise"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 2 Aug 26 +41
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Security disclosure: fail → unverified ▼ functional
    • License: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → good ▲ functional
    • Licence: MIT functional
  • 31 Jul 26 −27
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 53

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 2 exposed · ~167 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
check_ip ~105

Check if an IP address is internet background noise or potentially targeted activity. GreyNoise tracks IPs that mass-scan the internet. If an IP is 'noise', traffic from it is likely untargeted scanning. If it's NOT noise, traffic may be targeted at you specifically. RIOT dataset contains known-good IPs (CDNs, DNS servers, etc.).

NameTypeReqDescription
ipstringyesIPv4 address to check (e.g., 8.8.8.8)

No output schema declared.

No examples provided.

check_ips ~62

Check multiple IP addresses against GreyNoise in one call. Useful for triaging a list of suspicious IPs from logs or alerts. Rate limits apply (50/day for free tier).

NameTypeReqDescription
ipsarrayyesArray of IPv4 addresses to check (max 10)

No output schema declared.

No examples provided.