io.github.nickjlucker/greynoise
NPM · MCP-GREYNOISE · SCANNED SEP 22
MCP server for GreyNoise API - Check if IPs are internet background noise or targeted attacks
Available components
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 205 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.nickjlucker/greynoise MCP server?
io.github.nickjlucker/greynoise runs locally as an npm package, launched with npx -y mcp-greynoise. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-greynoise
claude mcp add nickjlucker-greynoise -- npx -y mcp-greynoise
{
"mcpServers": {
"nickjlucker-greynoise": {
"command": "npx",
"args": [
"-y",
"mcp-greynoise"
]
}
}
} {
"servers": {
"nickjlucker-greynoise": {
"command": "npx",
"args": [
"-y",
"mcp-greynoise"
]
}
}
} codex mcp add nickjlucker-greynoise -- npx -y mcp-greynoise
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nickjlucker-greynoise": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-greynoise"
],
"enabled": true
}
}
} openclaw mcp add nickjlucker-greynoise --command npx --arg -y --arg mcp-greynoise
mcp_servers:
nickjlucker-greynoise:
command: "npx"
args: ["-y", "mcp-greynoise"] {
"McpServers": {
"nickjlucker-greynoise": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-greynoise"
]
}
}
} assistant mcp add nickjlucker-greynoise -t stdio -c npx -a -y mcp-greynoise
{
"mcpServers": {
"nickjlucker-greynoise": {
"command": "npx",
"args": [
"-y",
"mcp-greynoise"
]
}
}
} 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.
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
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 22 Sept 2026 · Analysed npm/mcp-greynoise@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.).
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 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).
| Name | Type | Req | Description |
|---|---|---|---|
| ips | array | yes | Array of IPv4 addresses to check (max 10) |
No output schema declared.
No examples provided.
What is the io.github.nickjlucker/greynoise MCP server?
io.github.nickjlucker/greynoise is an MCP server listed in the public MCP registry as io.github.nickjlucker/greynoise. MCP server for GreyNoise API - Check if IPs are internet background noise or targeted attacks. This page covers its npm package (mcp-greynoise).
Is the io.github.nickjlucker/greynoise MCP server safe to use?
io.github.nickjlucker/greynoise scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.nickjlucker/greynoise MCP server expose?
io.github.nickjlucker/greynoise exposes 2 tools: check_ip, check_ips. Their descriptions and schemas cost roughly 167 tokens of context every time the server is loaded.
Is the io.github.nickjlucker/greynoise MCP server still maintained?
io.github.nickjlucker/greynoise is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.nickjlucker/greynoise MCP server under?
io.github.nickjlucker/greynoise declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.