FOFA Quake Hunter

Provides unified access to FOFA, Quake, and Hunter platforms for asset queries via MCP with AI-friendly configuration.

other

GitHub Stars

other

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "ruoji6-fofa_quake_hunter_mcp": {
      "command": "uvx",
      "args": [
        "fofa-quake-hunter-mcp"
      ],
      "env": {
        "FOFA_KEY": "your_fofa_api_key",
        "QUAKE_KEY": "your_quake_api_key",
        "FOFA_EMAIL": "your_email@example.com",
        "HUNTER_KEY": "your_hunter_api_key"
      }
    }
  }
}

This MCP server unifies access to FOFA, Quake, and Hunter cyberspace mapping platforms, enabling you to query assets from multiple sources through a single configurable Service Context Protocol interface. You can tailor the setup to include one or more platforms, control result sizing and fields, and interact with the services via familiar MCP client tools.

How to use

To use this MCP server, configure your MCP client with the provided server entry and start the MCP server through your preferred orchestration flow. You can then issue queries to FOFA, Quake, or Hunter using your client’s natural language or structured syntax, depending on the platform, and receive results from the integrated data sources.

How to install

Prerequisites: ensure you have a Python environment and a compatible MCP client installed. You will also need access keys for FOFA, Quake, and Hunter.

Install the MCP server using one of the supported methods.

uvx fofa-quake-hunter-mcp

Configuration and usage notes

Configure the MCP client to point at the FOFA-Quake-Hunter MCP server by adding an mcpServers entry that uses uvx to launch the MCP process and passes the required API keys through environment variables.

Example configuration in your MCP client (adjust paths to your environment):

{
  "mcpServers": {
    "fofa-quake-hunter": {
      "command": "uvx",
      "args": ["fofa-quake-hunter-mcp"],
      "env": {
        "FOFA_EMAIL": "your_email@example.com",
        "FOFA_KEY": "your_fofa_api_key",
        "QUAKE_KEY": "your_quake_api_key",
        "HUNTER_KEY": "your_hunter_api_key"
      }
    }
  }
}

At-a-glance configuration options

You can choose to configure one or more platforms. If a platform is not configured, the MCP client will provide a friendly prompt when attempting to use it.

Using API keys securely

Keep API keys secret. Store them in secure environment variable vaults or secret management systems as appropriate for your deployment. Rotate keys periodically and restrict permissions to only the necessary endpoints.

Troubleshooting

If commands fail to start, verify that your MCP client can reach the uvx binary, the MCP configuration JSON is valid, and that all required API keys are present in the environment.

Documentation and support notes

This guide provides practical steps to install, configure, and run the MCP server. For issues, submit tickets with your environment details and logs to help with debugging.

Available tools

fofa_search

Query FOFA cyberspace mapping platform with parameters like query, size, page, and fields to return results.

quake_search

Query Quake platform with parameters including query, include/exclude fields, pagination, and time range.

hunter_search

Query Hunter platform using structured field queries, with pagination and field selection.

Built by

VeilStrat

AI signals for GTM teams