Ioc Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Not applicable | |
| PORT | No | Not applicable | |
| API_KEY | Yes | API 密钥 (API Key) for authenticating with the Ioc Search API |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ip_address_searchA | Provides comprehensive analysis for a given IP address, including associated ASN, geographic location, network details, WHOIS information, and security vendor evaluations. Summarizes malicious, suspicious, harmless, and undetected classifications, enabling effective threat detection and risk assessment. |
| hash_searchB | Provides detailed threat analysis for a given hash, including analysis date, reputation, categories, security vendor assessments, threat names, and URL details. Detects malware, suspicious activity, and clean results from various security vendors with statistical summaries. |
| domain_searchC | Analyzes a given domain to provide insights into DNS records, HTTP certificate details, reputation, security vendor evaluations, and related tags. Includes detailed security classifications and supports identifying malicious or suspicious domains effectively. |
| url_searchB | Provides in-depth threat analysis for a given URL, including reputation scores, categories, security vendor evaluations, threat names, and metadata. Offers detailed insights into malicious, suspicious, and harmless classifications from various sources, helping to identify potential risks effectively. |
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 4 tools
Each tool has a clearly distinct purpose targeting a specific type of indicator: domain, hash, IP address, and URL. The descriptions reinforce this by detailing unique analysis aspects for each, such as DNS records for domains, hash categories for malware, geographic location for IPs, and URL metadata. There is no overlap or ambiguity in their functions.
All tool names follow a consistent pattern of 'noun_search' (domain_search, hash_search, ip_address_search, url_search), using snake_case uniformly. This predictable naming scheme makes it easy for agents to understand and select the appropriate tool based on the indicator type.
With 4 tools, the server is well-scoped for its purpose of IOC (Indicator of Compromise) search, covering the core indicator types: domain, hash, IP address, and URL. Each tool earns its place by providing specialized analysis, and the count is neither too thin nor excessive for the domain.
The tool set offers complete coverage for IOC search, including all major indicator types used in threat intelligence and security analysis. There are no gaps in the surface; agents can analyze domains, hashes, IPs, and URLs effectively, with detailed insights into reputation, security evaluations, and classifications from each tool.