Skip to main content
Glama
CorbettCajun

SpiderFoot MCP Server

Start Scan

spiderfoot_start_scan

Launch a new OSINT reconnaissance scan against a target to gather intelligence, investigate threats, or perform footprinting using SpiderFoot modules.

Instructions

Start a new scan against a target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scannameYes
scantargetYes
modulelistNo
typelistNo
usecaseNo

Implementation Reference

  • Zod input schema (StartScanSchema) for the spiderfoot_start_scan tool, defining parameters: scanname, scantarget (required), modulelist, typelist, usecase (optional). Used in both server registrations.
    const StartScanSchema = z.object({
      scanname: z.string().min(1),
      scantarget: z.string().min(1),
      modulelist: z.string().optional(),
      typelist: z.string().optional(),
      usecase: z.enum(['all', 'investigate', 'passive', 'footprint']).optional(),
    });
  • src/index.ts:70-81 (registration)
    Registration of spiderfoot_start_scan MCP tool in stdio server (index.ts), includes input schema reference, inline handler logic (env check + sf.startScan call), and output formatting.
      'spiderfoot_start_scan',
      { title: 'Start Scan', description: 'Start a new scan against a target.', inputSchema: StartScanSchema.shape },
      async (input) => {
        const allow = (process.env.ALLOW_START_SCAN ?? 'true').toLowerCase();
        if (!(allow === 'true' || allow === '1' || allow === 'yes')) {
          return { content: [{ type: 'text', text: 'Starting scans is disabled by configuration (ALLOW_START_SCAN=false).' }], isError: true };
        }
        const res = await sf.startScan(input as any);
        return { content: [{ type: 'text', text: JSON.stringify(res) }] };
      }
    );
  • Registration of spiderfoot_start_scan MCP tool in HTTP server (index-http.ts), identical to stdio version: schema ref, inline handler with env check and sf.startScan delegation.
    server.registerTool(
      'spiderfoot_start_scan',
      { title: 'Start Scan', description: 'Start a new scan against a target.', inputSchema: StartScanSchema.shape },
      async (input) => {
        const allow = (process.env.ALLOW_START_SCAN ?? 'true').toLowerCase();
        if (!(allow === 'true' || allow === '1' || allow === 'yes')) {
          return { content: [{ type: 'text', text: 'Starting scans is disabled by configuration (ALLOW_START_SCAN=false).' }], isError: true };
        }
        const res = await sf.startScan(input as any);
        return { content: [{ type: 'text', text: JSON.stringify(res) }] };
      }
    );
  • Core helper implementation: startScan method in SpiderfootClient HTTP wrapper. Performs POST /startscan to underlying Spiderfoot server with provided args and returns response.
    async startScan(args: {
      scanname: string;
      scantarget: string;
      modulelist?: string; // comma separated module names
      typelist?: string;   // comma separated event types
      usecase?: string;    // all|investigate|passive|footprint
    }) {
      const { data } = await this.http.post('/startscan', args);
      return data;
    }
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 the tool starts a scan but doesn't mention critical traits such as whether this is a long-running operation, what permissions are required, potential rate limits, or what happens if a scan with the same name exists. This leaves significant gaps in understanding the tool's 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 extremely concise with a single sentence that directly states the tool's purpose. It is front-loaded with no wasted words, making it easy to parse quickly. This efficiency is appropriate for a simple action, though it sacrifices detail for brevity.

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

Completeness2/5

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

Given the complexity of starting a scan (a potentially resource-intensive operation), no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't address key aspects like expected return values, error conditions, or operational constraints, making it inadequate for safe and effective use by an agent.

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

Parameters2/5

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

The input schema has 0% description coverage, so the description must compensate by explaining parameters. It adds no meaning beyond the schema, failing to clarify what 'scanname', 'scantarget', 'modulelist', 'typelist', or 'usecase' represent. For example, it doesn't indicate if 'scantarget' is a URL, IP address, or domain, leaving parameters largely undocumented.

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

Purpose4/5

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

The description clearly states the action ('Start a new scan') and target ('against a target'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'spiderfoot_scans' or 'spiderfoot_scan_info', which might also relate to scan operations, leaving some ambiguity about its unique role.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., whether a target must be pre-configured) or comparisons to sibling tools like 'spiderfoot_scans' (which might list scans) or 'spiderfoot_scan_data' (which might retrieve results). This omission leaves the agent without clear usage direction.

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