Kaspersky OpenTIP MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENTIP_API_KEY | Yes | Your OpenTIP API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_hashA | Get threat intelligence information about a file by hash (md5, sha1, sha256) |
| search_domainB | Get threat intelligence data about a web domain |
| search_ipB | Get threat intelligence data about an IP address |
| search_urlA | Get threat intelligence data about a URL |
| get_full_analysis_resultB | Get full analysis results for a file that was submitted via the web portal. |
| analyze_fileC | Submit a file for basic analysis using the OpenTIP API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have distinct purposes (analyze_file vs search_*), but get_full_analysis_result is ambiguous because it only retrieves results for web portal submissions, not for files submitted via analyze_file. This creates potential confusion about the analysis workflow.
All tools follow a consistent verb_noun pattern in snake_case (e.g., analyze_file, search_domain). Even the longer get_full_analysis_result maintains the pattern.
Six tools is well-scoped for a threat intelligence server, covering file analysis and searches for domains, hashes, IPs, and URLs. The count is neither too few nor too many.
The search tools cover key indicators, but the file analysis workflow is incomplete: no tool to retrieve results for files submitted via analyze_file, and no update or delete operations. This gap may cause agent failures when expecting a full analysis cycle.