Intel Threadlinqs MCP

Recent Threats

get_recent_threats

Read-onlyIdempotent

Retrieve recently published threat intelligence with pagination controls. Use limit, offset, or cursor to page through older threats and identify current security risks.

Instructions

List the most recently published threats. Paginated: pass limit (default 15, max 100) and offset to page through older threats; the result includes has_more and an opaque next_cursor (reusable as offset/cursor).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 15, max 100)
`cursor`	No	Opaque pagination cursor (next_cursor from a prior result). Decoded to an offset; ignored when offset is given.
`offset`	No	Row offset for pagination (default 0). Or pass cursor from a prior result.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`total`	No	Total matching rows, when the handler reports one.
`has_more`	No	True when another page may exist.
`next_cursor`	No	Opaque cursor for the next page, or null when this is the last page or the endpoint ignores offset.

Schema Changelog

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

Changed10 schema fields changedv8.1.1Aug 3, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque pagination cursor (next_cursor from a prior result). Decoded to an offset; ignored when offset is given.",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Number of threats to return (default 10, max 50)"New value: +"Max results (default 15, max 100)"

addedInput schema / properties / offset

Added value: +{
+  "description": "Row offset for pagination (default 0). Or pass cursor from a prior result.",
+  "type": "number"
+}

removedOutput schema / properties / count

Removed value: -{
-  "type": "number"
-}

addedOutput schema / properties / data

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "category": {
+        "type": "string"
+      },
+      "created_at": {
+        "type": "string"
+      },
+      "detection_count": {
+        "type": "integer"
+      },
+      "id": {
+        "description": "Threat ID (TL-YYYY-NNNN) — pass to get_threat.",
+        "type": "string"
+      },
+      "ioc_count": {
+        "type": "integer"
+      },
+      "severity": {
+        "type": "string"
+      },
+      "threat_actor": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / has_more

Added value: +{
+  "description": "True when another page may exist.",
+  "type": "boolean"
+}

removedOutput schema / properties / items
```
Removed value: -{
-  "type": "array"
-}
```

addedOutput schema / properties / next_cursor

Added value: +{
+  "description": "Opaque cursor for the next page, or null when this is the last page or the endpoint ignores offset.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / total

Added value: +{
+  "description": "Total matching rows, when the handler reports one.",
+  "type": "integer"
+}

addedOutput schema / required
```
Added value: +[
+  "data"
+]
```

First observedv0.1.0Jul 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds meaningful value by explaining pagination behavior — that next_cursor is opaque, reusable as offset/cursor, and that offset/cursor interplay ('ignored when offset is given') — which goes beyond what annotations provide.

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, zero wasted words. The description front-loads the core purpose in the first clause, then packs the pagination contract concisely. Every phrase ('opaque', 'reusable as offset/cursor') earns its place.

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 a valid output schema, high schema coverage, and strong annotations, the description is nearly complete. It explains the essential pagination contract clearly. The only minor gap is not naming alternatives explicitly, but for a paginated list tool this is adequate.

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 parameters are fully documented in the schema. The description adds value by clarifying the relationship between cursor and offset (cursor decoded to offset, ignored when offset given) and describing the has_more/next_cursor return format, which compensates meaningfully beyond the schema alone.

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+resource ('List the most recently published threats') and adds the pagination scope detail. It distinguishes from siblings like get_threat (single), search_threats (search filter), and get_similar_threats (similarity) by emphasizing 'recently published' ordering.

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 description and parameter docs explain pagination mechanics (limit, offset, cursor, has_more, next_cursor). It doesn't explicitly state when to prefer this over search_threats vs get_threat, but the 'most recently published' framing and pagination semantics give clear usage context without naming alternatives.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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