greynoise-mcp-server

Official

by GreyNoise-Intelligence

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Tag Activity

get-tag-activity

Read-only

Retrieve time-series unique-IP counts and intention activity for a security tag (by ID/slug) or CVE. Specify activity period of 1, 10, or 30 days with hourly or daily granularity.

Instructions

Retrieve time-series unique-IP counts and intention activity for a tag (by id/slug) or by CVE, from v3/tags/{id}/activity. Provide exactly one of id_or_slug or cve. days must be 1, 10, or 30 (default 30); granularity is 1h for 1 day, else 24h.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cve`	No	CVE identifier to retrieve activity for (matches associated tags)
`days`	No	Days of activity: 1, 10, or 30	30
`id_or_slug`	No	Tag ID or slug to retrieve activity for

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.4Jul 23, 2026

addedOutput schema / properties / results / items / properties / activity / properties / activity

Added value: +{
+  "additionalProperties": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "active_ips": {
+          "type": "number"
+        },
+        "timestamp": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "timestamp",
+        "active_ips"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

removedOutput schema / properties / results / items / properties / activity / properties / timeline

Removed value: -{
-  "items": {
-    "additionalProperties": {},
-    "properties": {
-      "bucket": {
-        "type": "string"
-      },
-      "metrics": {
-        "additionalProperties": {},
-        "properties": {
-          "total_ips": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "total_ips"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "bucket",
-      "metrics"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

Changed4 schema fields changedv0.5.3Jul 21, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / cve / description

Previous value: -"CVE identifier to retrieve activity for"New value: +"CVE identifier to retrieve activity for (matches associated tags)"

changedInput schema / properties / days / description

Previous value: -"Number of days of activity to retrieve (must be 1, 10, or 30)"New value: +"Days of activity: 1, 10, or 30"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "results": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "activity": {
+            "additionalProperties": {},
+            "properties": {
+              "aggregations": {
+                "additionalProperties": {},
+                "properties": {
+                  "classification": {
+                    "additionalProperties": {
+                      "type": "number"
+                    },
+                    "propertyNames": {
+                      "type": "string"
+                    },
+                    "type": "object"
+                  },
+                  "total_ips": {
+                    "type": "number"
+                  }
+                },
+                "type": "object"
+              },
+              "slug": {
+                "type": "string"
+              },
+              "timeline": {
+                "items": {
+                  "additionalProperties": {},
+                  "properties": {
+                    "bucket": {
+                      "type": "string"
+                    },
+                    "metrics": {
+                      "additionalProperties": {},
+                      "properties": {
+                        "total_ips": {
+                          "type": "number"
+                        }
+                      },
+                      "required": [
+                        "total_ips"
+                      ],
+                      "type": "object"
+                    }
+                  },
+                  "required": [
+                    "bucket",
+                    "metrics"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              }
+            },
+            "type": "object"
+          },
+          "tag": {
+            "additionalProperties": {},
+            "properties": {
+              "category": {
+                "type": "string"
+              },
+              "cves": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "id": {
+                "type": "string"
+              },
+              "intention": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "slug": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "slug"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "tag",
+          "activity"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "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?

Annotations already declare readOnly and openWorld hints. The description adds value by detailing the output type (time-series IP counts and intention activity) and constraints on time range (days) and granularity (1h vs 24h). No contradictions.

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?

Two sentences, no filler. First sentence captures purpose and key constraint. Second sentence details parameter specifics. Well front-loaded.

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

Completeness5/5

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

Given three parameters (all described), high schema coverage, and presence of an output schema, the description sufficiently covers what the tool does, required inputs, and behavioral nuances. No gaps.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds critical usage semantics: the exclusivity constraint between 'id_or_slug' and 'cve', and the relationship between 'days' and 'granularity'. This goes beyond the schema's individual property descriptions.

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?

The description clearly states the verb 'Retrieve' and the specific resource 'time-series unique-IP counts and intention activity for a tag or by CVE'. It also highlights exclusivity of two parameters, distinguishing it from sibling tools like 'get-tag-details' or 'analyze-tags-activity'.

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

Usage Guidelines4/5

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

Explicitly states 'Provide exactly one of id_or_slug or cve' and specifies allowed values for 'days' with default. However, it does not explicitly compare with alternatives or mention when not to use it.

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