Skip to main content
Glama
scriptedstatement

opencti-mcp

search_threat_intel

Search OpenCTI for threat intelligence across indicators, threat actors, malware, techniques, CVEs, and reports. Filter by labels, dates, confidence, and pagination to refine results.

Instructions

Search OpenCTI for threat intelligence across all entity types (indicators, threat actors, malware, techniques, CVEs, reports).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results per entity type (default: 5, max: 20)
queryYesSearch term (IOC, threat actor name, malware, CVE, etc.)
labelsNoFilter by labels (e.g., ['tlp:amber', 'malicious'])
offsetNoSkip first N results (for pagination, max: 500)
created_afterNoFilter by created date >= (ISO format: 2024-01-01)
confidence_minNoMinimum confidence threshold (0-100)
created_beforeNoFilter by created date <= (ISO format: 2024-12-31)

Schema Changelog

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

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral burden. It states what the tool does but does not disclose whether it is read-only, how results are aggregated across entity types, any authorization assumptions, or rate limits. For a no-annotation tool, this is a notable gap.

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?

One clean, front-loaded sentence with no redundancy. It states the resource, the action, the scope, and useful examples of entity types in a compact way.

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

Completeness3/5

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

The schema documents all seven parameters, so a caller knows how to construct a request. However, there is no output schema and no description of the return shape or how multi-type results are packaged. The description is adequate for basic invocation but leaves the agent to guess about result structure and about why this broad tool may be preferable to a specialized sibling.

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?

Schema description coverage is 100%, and every parameter has a clear description, so the baseline is 3. The tool description adds no extra parameter context, but it does not need to since the schema already explains query, limit, labels, offset, date filters, and confidence threshold.

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 clear verb ('Search'), a resource ('OpenCTI'), and the full scope ('across all entity types'), with concrete examples. This clearly differentiates from the many specialized search_* siblings because it explicitly covers multiple entity types in one call.

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 gives a clear context for when to use the tool: broad, multi-entity threat intelligence searches. It does not explicitly name alternatives or say 'use search_threat_actor when you only need actors', so it stops short of a 5, but the sibling list and the phrase 'across all entity types' make the intended use clear.

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

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/scriptedstatement/opencti-mcp'

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