greynoise-mcp-server

Official

by GreyNoise-Intelligence

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

GNQL Metadata Query

gnql-metadata-query

Read-only

Query GreyNoise IP metadata with GNQL when you need classification and tags, not raw scan data; supports pagination and JSON/CSV output.

Instructions

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).

Results are paginated via the scroll token. Set quick=true to return only IP and classification/trust level.

Set format="csv" for spreadsheet-friendly CSV output (columns: ip, classification, actor, organization, source_country, tags, ports, bsi_found, bsi_name, bsi_trust_level); default "json" renders a Markdown summary. structuredContent is always the full JSON regardless of format.

Input Schema

Name	Required	Description	Default
`size`	No	Results per page (default: 25, max: 10000)
`query`	Yes	GNQL query string
`quick`	No	If true, return only IP and classification/trust level
`format`	No	Output format for the text response (default: json)	json
`scroll`	No	Pagination scroll token from a previous response

Output Schema

Name	Required	Description	Default
`data`	Yes
`request_metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.5Nov 2, 2026

changedOutput schema / properties / data / items / properties / business_service_intelligence / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "found": {
-        "anyOf": [
-          {
-            "type": "boolean"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "trust_level": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "found": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "trust_level": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed4 schema fields changedv0.5.4Jul 23, 2026

removedOutput schema / properties / data / items / properties / business_service_intelligence / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / data / items / properties / business_service_intelligence / anyOf

Added value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "found": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "trust_level": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / data / items / properties / business_service_intelligence / properties

Removed value: -{
-  "found": {
-    "type": "boolean"
-  },
-  "name": {
-    "type": "string"
-  },
-  "trust_level": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / data / items / properties / business_service_intelligence / type
```
Removed value: -"object"
```

Changed4 schema fields changedv0.5.3Jul 21, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / format / default
```
Added value: +"json"
```

changedInput schema / properties / format / description

Previous value: -"Output format (default: json)"New value: +"Output format for the text response (default: json)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "business_service_intelligence": {
+            "additionalProperties": {},
+            "properties": {
+              "found": {
+                "type": "boolean"
+              },
+              "name": {
+                "type": "string"
+              },
+              "trust_level": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "internet_scanner_intelligence": {
+            "additionalProperties": {},
+            "properties": {
+              "actor": {
+                "type": "string"
+              },
+              "classification": {
+                "type": "string"
+              },
+              "metadata": {
+                "additionalProperties": {},
+                "properties": {
+                  "organization": {
+                    "type": "string"
+                  },
+                  "source_country": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "raw_data": {
+                "additionalProperties": {},
+                "properties": {
+                  "scan": {
+                    "items": {
+                      "additionalProperties": {},
+                      "properties": {
+                        "port": {
+                          "type": "number"
+                        },
+                        "protocol": {
+                          "type": "string"
+                        }
+                      },
+                      "required": [
+                        "port",
+                        "protocol"
+                      ],
+                      "type": "object"
+                    },
+                    "type": "array"
+                  }
+                },
+                "type": "object"
+              },
+              "tags": {
+                "items": {
+                  "additionalProperties": {},
+                  "properties": {
+                    "intention": {
+                      "type": "string"
+                    },
+                    "name": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "name",
+                    "intention"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              }
+            },
+            "type": "object"
+          },
+          "ip": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "ip"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "request_metadata": {
+      "additionalProperties": {},
+      "properties": {
+        "adjusted_query": {
+          "type": "string"
+        },
+        "complete": {
+          "type": "boolean"
+        },
+        "message": {
+          "type": "string"
+        },
+        "query": {
+          "type": "string"
+        },
+        "restricted_fields": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "scroll": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "complete",
+        "query"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "request_metadata"
+  ],
+  "type": "object"
+}

First observedv0.4.0Jun 14, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial behavior beyond the readOnlyHint/openWorldHint annotations: pagination happens via a scroll token, quick=true truncates the payload, format='csv' changes only the text rendering, and structuredContent is invariant. It stops short of covering scroll-token expiry or error/rate-limit behavior, which would be the remaining useful disclosure for a paginated search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The differentiator against gnql-query is front-loaded in the first sentence, followed by short scoped paragraphs for pagination, quick mode, and format. No sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and the description covers the non-obvious parts: pagination, truncation, and output-format invariance. The one gap is that 'GNQL query syntax' is only referenced by pointer to gnql-query rather than characterized, leaving an agent to infer query construction.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description exceeds it by enumerating the exact CSV columns produced by format='csv' and clarifying that format affects only the text response while structuredContent stays JSON. That is meaning the schema's one-line enum description does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search GreyNoise data using GNQL, returning IP metadata without raw scan data') and explicitly contrasts the result payload against the sibling gnql-query. The distinction is resolvable without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the positive condition ('when you need IP classification, tags, and metadata but not raw scan details') and the excluded payload ('ports, fingerprints, HTTP paths'), plus names gnql-query as the heavier alternative. This is explicit when/when-not/alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server