greynoise-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GREYNOISE_API_KEY | Yes | Your GreyNoise Enterprise API key |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-tag-listA | Retrieve the complete list of GreyNoise tags. Metadata for each tag includes:
|
| search-tagsC | Search GreyNoise Tags by various criteria |
| get-tag-detailsC | Get detailed information about a specific GreyNoise tag |
| get-tag-activityC | Retrieve time-series that includes unique IP counts and intention activity data for a specific GreyNoise tag or by CVE |
| analyze-tags-activityC | Analyze activity for multiple tags and provide a summary |
| get-trending-vulnerabilitiesA | Get a list of currently trending vulnerability tags and anomalies from GreyNoise |
| lookup-ip-contextB | Get detailed GreyNoise context information about an IP address |
| quick-check-ipA | Get a fast, lightweight check of an IP address from GreyNoise |
| multi-ip-checkA | Check multiple IP addresses at once for scanner intelligence and business service classification |
| gnql-statsA | Get aggregate statistics for results matching a GreyNoise GNQL query. GNQL (GreyNoise Query Language) is a domain-specific query language that uses Lucene deep under the hood. Facets:
Behavior:
Shortcuts:
Examples:
|
| gnql-queryA | Search GreyNoise data using GNQL (GreyNoise Query Language). Returns full IP context results including raw scan data. GNQL is a domain-specific query language that uses Lucene deep under the hood. Facets:
Examples:
Results are paginated. Use the scroll parameter to retrieve additional pages. |
| gnql-metadata-queryA | Search GreyNoise data using GNQL, returning IP metadata without raw scan data. Lighter and faster than gnql-query. Supports the same GNQL query syntax as gnql-query. Use this when you need IP classification, tags, and metadata but not raw scan details (ports, fingerprints, HTTP paths). Supports CSV output format via the format parameter. Results are paginated. |
| gnql-timeseriesA | Retrieve hourly GNQL records for a time range. Enables temporal analysis of IP activity matching any GNQL query (Recall). Returns IP records bucketed by hour, useful for investigating when specific IPs were active and what they were doing. |
| gnql-timeseries-statsA | Get the number of unique IPs matching a GNQL query per hour/day over a time range (Recall Stats). Returns aggregated counts of unique IPs per time bucket, useful for trend analysis and understanding how scanning/attack activity changes over time. |
| get-cve-detailsB | Get detailed information about a specific CVE from GreyNoise |
| get-sessionA | Get full metadata and connection details for a single GreyNoise sensor session by its ID. Returns source/destination IPs and ports, timestamps, byte/packet counts, classification, and any additional enrichment fields. |
| get-session-pcapA | Download the raw PCAP capture for a single GreyNoise sensor session. Saves the binary PCAP file to a temporary directory and returns the file path. The file can be opened with Wireshark, tshark, or tcpdump. |
| export-sessions-pcapA | Export a PCAP file containing packets from multiple GreyNoise sensor sessions matching query criteria. Saves the binary PCAP to a temporary directory and returns the file path. The file can be opened with Wireshark, tshark, or tcpdump. Use Lucene query syntax to filter sessions (e.g., "destination.port:443", "source.ip:1.2.3.4"). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| vendor-threat-report | Generate a comprehensive threat report for a vendor technology |
| ip-threat-analysis | Generate a detailed analysis of an IP address to determine if it's malicious and associated threats |
| cve-analysis | Generate a comprehensive analysis of a CVE including exploitation status and risk assessment |
| emerging-threat-report | Generate a report on emerging threats based on recent activity and trending data |
| security-posture-assessment | Generate a security posture assessment for an organization based on technologies and vulnerabilities |
| threat-hunting | Generate a threat hunting plan based on specific indicators or patterns |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GreyNoise-Intelligence/greynoise-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server