Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

by threadlinqs-cmd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

CVE Intelligence

get_cve_intelligence
Read-onlyIdempotent

Retrieve a composite CVE dossier in one call: enriched details, referenced threats, attributed actors, MITRE techniques, weaponization velocity, related CVEs, and detections.

Instructions

Composite CVE dossier in one call: the enriched CVE detail, the threats that reference it (authoritative join — cve.threat_ids is reconciled to it), the attributed actors and MITRE techniques behind those threats, weaponization velocity for THIS CVE with its rank against the corpus, CWE-sibling related CVEs, and detections that name it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cve_idYesCVE identifier (e.g. CVE-2024-3400)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cveNo
mitreNo
actorsNo
threatsNo
related_cvesNo
velocity_dataNo
related_detectionsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv8.2.1
    • addedOutput schema / properties / actors
      Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "actor": {
+        "type": "string"
+      },
+      "threat_count": {
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / cve / properties / threat_ids
      Added value: +{
+  "items": {
+    "description": "Reconciled from threats.cve_list — the authoritative join. Pass to get_threat.",
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / cve / properties / threat_ids_note
      Added value: +{
+  "description": "Present only when the derived cve_details reverse index disagreed.",
+  "type": "string"
+}
    • addedOutput schema / properties / cve / properties / threat_ids_source
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / mitre
      Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "tactic": {
+        "type": "string"
+      },
+      "technique": {
+        "type": "string"
+      },
+      "technique_id": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / related_cves
      Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "cve_id": {
+        "type": "string"
+      },
+      "is_kev": {
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / threats
      Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "actor": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "severity": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / velocity_data / additionalProperties
      Added value: +true
    • addedOutput schema / properties / velocity_data / properties
      Added value: +{
+  "cohort_fastest": {
+    "items": {},
+    "type": "array"
+  },
+  "corpus": {
+    "additionalProperties": true,
+    "properties": {
+      "avg_velocity": {
+        "type": "number"
+      },
+      "total": {
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "cve": {
+    "description": "The velocity row for THIS CVE (velocity_days = publication → first tracked threat), or null when it has no tracked linkage.",
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "note": {
+    "type": "string"
+  },
+  "rank": {
+    "description": "{faster_than_pct, position, of} — where this CVE sits in the corpus velocity distribution.",
+    "type": [
+      "object",
+      "null"
+    ]
+  }
+}
    • changedOutput schema / properties / velocity_data / type
      Previous value: -[
-  "object",
-  "null"
-]New value: +"object"
  2. Changed4 schema fields changedv8.1.1
    • changedInput schema / properties / cve_id / description
      Previous value: -"CVE ID (e.g. CVE-2025-12345)"New value: +"CVE identifier (e.g. CVE-2024-3400)"
    • addedOutput schema / properties / cve
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "cve_id": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / related_detections
      Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
    • addedOutput schema / properties / velocity_data
      Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description adds valuable behavioral nuance: it explains the authoritative join on cve.threat_ids, the reconciliation of attributed actors and techniques, and the corpus-relative weaponization rank. This clearly matches the non-destructive read annotation with no contradiction.

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

Conciseness4/5

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

The description is front-loaded with the high-level concept 'Composite CVE dossier in one call' and then enumerates the contained components. It is dense and somewhat list-like, but every component listed contributes to understanding what the tool provides.

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?

For a tool with one required parameter, an output schema, and read-only/idempotent annotations, the description is complete. It clearly communicates the full scope of the returned intelligence including threats, actors, techniques, velocity ranking, sibling CVEs, and detections, so an agent is well-equipped to select and invoke it correctly.

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

Parameters3/5

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

The input schema already fully documents the single cve_id parameter with an example, so schema coverage is 100%. The description adds no additional parameter-level meaning, making the schema-based baseline of 3 appropriate.

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: 'Composite CVE dossier in one call' with a detailed inventory of what it returns. This clearly distinguishes it from singular tools like get_cve or get_cwe by emphasizing the aggregated, cross-referenced payload.

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?

The phrase 'Composite CVE dossier in one call' gives clear context for when this tool is appropriate: when you need a broad CVE intelligence bundle rather than a single detail. It does not explicitly name alternative tools or exclusion conditions, so it stops short of a full 5.

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

Install Server

Other Tools

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/threadlinqs-cmd/intelthreadlinqs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server