Skip to main content
Glama
CorbettCajun

SpiderFoot MCP Server

Modules

spiderfoot_modules

List available SpiderFoot modules to discover reconnaissance capabilities for OSINT investigations.

Instructions

List available SpiderFoot modules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:45-49 (registration)
    Registration of the 'spiderfoot_modules' MCP tool. The handler fetches modules via the SpiderfootClient and returns JSON.
    server.registerTool(
      'spiderfoot_modules',
      { title: 'Modules', description: 'List available SpiderFoot modules.', inputSchema: {} },
      async () => ({ content: [{ type: 'text', text: JSON.stringify(await sf.modules()) }] })
    );
  • Core handler function in SpiderfootClient that performs HTTP GET /modules to retrieve the list of available SpiderFoot modules.
    async modules() {
      const { data } = await this.http.get('/modules');
      return data;
    }
  • Registration of the 'spiderfoot_modules' MCP tool in the HTTP server variant. Identical to stdio version.
    server.registerTool(
      'spiderfoot_modules',
      { title: 'Modules', description: 'List available SpiderFoot modules.', inputSchema: {} },
      async () => ({ content: [{ type: 'text', text: JSON.stringify(await sf.modules()) }] })
    );
  • Helper function to create the SpiderfootClient instance from environment variables, used by the tool handler.
    export function makeSpiderfootClientFromEnv() {
      const baseUrl = process.env.SPIDERFOOT_BASE_URL || 'http://127.0.0.1:5001';
      const username = process.env.SPIDERFOOT_USER;
      const password = process.env.SPIDERFOOT_PASS;
      return new SpiderfootClient({ baseUrl, username, password });
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'lists' modules, implying a read-only operation, but does not specify details like response format, pagination, or error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It is front-loaded and wastes no words, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavior, output, or usage context, which could be helpful for an agent. It meets the baseline for a simple list tool but does not excel.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, earning a baseline score of 4 for not adding unnecessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and the resource ('available SpiderFoot modules'), making the purpose specific and unambiguous. It distinguishes itself from siblings like 'spiderfoot_scans' (which lists scans) or 'spiderfoot_event_types' (which lists event types), focusing specifically on modules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context (e.g., before starting a scan), or exclusions, leaving the agent to infer usage based on the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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