FOFA Quake Hunter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOFA_KEY | No | Your FOFA API key. Required for FOFA search tools. Obtain from https://fofa.info → Personal Center. | |
| QUAKE_KEY | No | Your Quake API key. Required for Quake search tools. Obtain from https://quake.360.net → Personal Center → Key Management. | |
| FOFA_EMAIL | No | Your FOFA account email. Required for FOFA search tools. Obtain from https://fofa.info → Personal Center. | |
| HUNTER_KEY | No | Your Hunter API key. Required for Hunter search tools. Obtain from https://hunter.qianxin.com → Personal Center → API Management. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fofa_searchA | Search FOFA cyberspace mapping platform. Requires FOFA_EMAIL and FOFA_KEY environment variables. Query syntax: field="value" format. Matching operators: = (match), == (exact match), != (not match), *= (fuzzy match with wildcards). Logical operators: && (AND), || (OR). Examples: body="miner start", server=="nginx", domain="example.com" && port="443" |
| quake_searchA | Search Quake 360 cyberspace mapping platform using scroll API (supports deep pagination). Requires QUAKE_KEY environment variable. Query syntax: field:value format (e.g., port:443, title:"keyword"). Logical operators: AND, OR, NOT (uppercase). Examples: port:443, ip:1.1.1.1 AND port:80, service:http AND NOT response:"baidu". IMPORTANT: Use 'include' parameter to specify which fields to return. NOTE: Field names must be exact - use 'asn' and 'org' (NOT 'as_org'), use specific component fields like 'components.product_name_cn' (NOT just 'components'). Supports pagination_id for getting more pages. |
| hunter_searchA | Search Hunter (奇安信鹰图) cyberspace mapping platform. Requires HUNTER_KEY environment variable. Query syntax: field="value" format. Matching operators: = (fuzzy match), == (exact match), != (fuzzy exclude), !== (exact exclude). Logical operators: && (AND), || (OR). Examples: web.body="keyword", web.title=="login", domain="example.com" && web.status_code="200", ip!="1.1.1.1". Supports filtering by asset type: web assets, non-web assets, or all. Supports time range filtering (querying beyond 30 days will consume extra credits). |
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 3 tools
Each tool has a clearly distinct purpose targeting a different cyberspace mapping platform: fofa_search for FOFA, hunter_search for Hunter, and quake_search for Quake 360. There is no overlap in functionality as they operate on separate data sources with unique query syntax and parameters.
All tool names follow a consistent pattern: platform name (fofa, hunter, quake) followed by '_search'. This uniform verb_noun structure makes the tool set predictable and easy to understand.
With 3 tools, the count is well-scoped for the server's purpose of querying multiple cyberspace mapping platforms. Each tool earns its place by covering a distinct platform, avoiding redundancy while providing comprehensive coverage of the domain.
The tool set is complete for its intended domain, offering search capabilities across three major cyberspace mapping platforms (FOFA, Hunter, Quake 360). There are no obvious gaps, as each tool provides the core functionality needed to query its respective platform with detailed syntax and parameter support.