SpiderFoot FAQs

Question 1

What is SpiderFoot MCP Server?

Accepted Answer

SpiderFoot MCP Server acts as an integration layer, exposing local SpiderFoot functionality (its web UI/API) as accessible tools via the Model Context Protocol (MCP). This enables seamless interaction with various MCP-compatible clients and IDEs.

Question 2

Can I control the initiation of new SpiderFoot scans?

Accepted Answer

Yes, the `ALLOW_START_SCAN` environment variable provides configurable control. You can set it to `true` or `false` to enable or disable the `spiderfoot_start_scan` tool, giving you full control over initiating new scans through the MCP server.

Question 3

What SpiderFoot functionalities does it expose?

Accepted Answer

It exposes core SpiderFoot API functions, including scan management (`spiderfoot_start_scan`, `spiderfoot_scans`), data retrieval (`spiderfoot_scan_data`, `spiderfoot_event_types`), module listing, and basic connectivity checks, simplifying OSINT operations.

Question 4

How does it integrate with development environments and clients?

Accepted Answer

The server supports both Stdio and HTTP transport mechanisms, offering flexible integration. IDEs or MCP clients can either launch the server locally (stdio) or connect to a running instance (HTTP), with detailed configuration examples provided for popular tools.

Question 5

Is SpiderFoot MCP Server easy to deploy?

Accepted Answer

Yes, it's designed for streamlined deployment. It includes a `Dockerfile` and `docker-compose.yml` for Dockerized setup, allowing for quick and efficient integration into existing development and security environments.

SpiderFoot

SpiderFoot

主な機能

ユースケース

主な機能

ユースケース