hunter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUNTER_API_KEY | Yes | Your Qianxin Hunter API key, obtained from https://hunter.qianxin.com personal center. | |
| DEFAULT_BATCH_FIELDS | No | Default return fields for batch/export interfaces. Optional. | |
| DEFAULT_SEARCH_FIELDS | No | Default return fields for hunter_search interface. Optional. | |
| DEFAULT_BATCH_SAVE_DIR | No | Default download directory for exported files. Optional. |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hunter_searchA | 使用 Qianxin Hunter（奇安信鹰图平台）语法查询网络空间测绘数据（小批量实时查询）。若只关心资产数量，请设置 fields="ip,port,domain"，page_size=1。 |
| hunter_batch_task_createA | 创建 Qianxin Hunter 批量查询任务，任务将以异步方式导出数据为csv。支持通过上传文件(file_path)对批量的ip/domain/company进行资产查询和结果导出，或通过搜索语法(search)进行资产查询和结果导出。成功调用后将返回 task_id，用于后续查询进度和下载文件。 |
| hunter_batch_task_progressA | 查看 Qianxin Hunter 批量查询任务的执行进度。 |
| hunter_batch_task_result_downloadA | 下载 Qianxin Hunter 批量查询的导出文件（CSV格式），保存到本地。注意：需先使用 hunter_batch_task_progress 确认任务已完成。 |
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 distinct purpose: batch task creation, progress checking, result download, and real-time search. No overlap or ambiguity.
All tools follow the 'hunter_verb_noun' pattern with snake_case, e.g., hunter_batch_task_create, hunter_search. Fully consistent.
Four tools cover the core workflows (batch tasks lifecycle and direct search) without redundancy. Well-scoped for the server's purpose.
Covers key operations: batch task create, progress check, download, and real-time search. Minor gap in lacking a direct single-asset query, but real-time search handles it.