Schema | SpiderFoot MCP Server

SpiderFoot MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MCP_HTTP_PORT`	No	Port for HTTP transport (if using index-http.ts)	3000
`SPIDERFOOT_PASS`	No	Optional HTTP Digest password if you enable auth in SpiderFoot
`SPIDERFOOT_USER`	No	Optional HTTP Digest username if you enable auth in SpiderFoot
`ALLOW_START_SCAN`	No	Enables/disables spiderfoot_start_scan tool	true
`SPIDERFOOT_BASE_URL`	No	Base URL of your SpiderFoot web UI/API	http://127.0.0.1:5001

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.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
spiderfoot_pingA	Ping SpiderFoot server to verify it is responding.
spiderfoot_modulesA	List available SpiderFoot modules.
spiderfoot_event_typesB	List available SpiderFoot event types.
spiderfoot_scansB	List all scans (past and present).
spiderfoot_scan_infoC	Retrieve scan metadata/config for a scan ID.
spiderfoot_start_scanC	Start a new scan against a target.
spiderfoot_scan_dataC	Fetch scan event results for a scan ID.
spiderfoot_scan_data_uniqueC	Fetch unique scan event results.
spiderfoot_scan_logsC	Fetch/poll scan logs for a given scan ID.
spiderfoot_export_jsonC	Export scan results in JSON for CSV of IDs.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CorbettCajun/Spiderfoot-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server