spiderfoot_scan_data
Retrieve scan event results for a specific scan ID to analyze reconnaissance data from SpiderFoot OSINT investigations.
Instructions
Fetch scan event results for a scan ID.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| eventType | No |
Implementation Reference
- src/spiderfootClient.ts:60-66 (handler)Core handler logic for fetching scan event results via HTTP POST to SpiderFoot API endpoint '/scaneventresults'. This is called by the tool's wrapper handler.async scanEventResults(args: { id: string; eventType?: string }) { const { data } = await this.http.post('/scaneventresults', { id: args.id, eventType: args.eventType ?? 'ALL', }); return data; }
- src/index.ts:82-86 (registration)Tool registration for 'spiderfoot_scan_data' in the stdio MCP server, including input schema (id: string, optional eventType) and handler wrapper.server.registerTool( 'spiderfoot_scan_data', { title: 'Scan Data', description: 'Fetch scan event results for a scan ID.', inputSchema: { id: z.string(), eventType: z.string().optional() } }, async ({ id, eventType }) => ({ content: [{ type: 'text', text: JSON.stringify(await sf.scanEventResults({ id, eventType })) }] }) );
- src/index-http.ts:66-70 (registration)Tool registration for 'spiderfoot_scan_data' in the HTTP MCP server, identical to stdio version.server.registerTool( 'spiderfoot_scan_data', { title: 'Scan Data', description: 'Fetch scan event results for a scan ID.', inputSchema: { id: z.string(), eventType: z.string().optional() } }, async ({ id, eventType }) => ({ content: [{ type: 'text', text: JSON.stringify(await sf.scanEventResults({ id, eventType })) }] }) );
- src/index.ts:23-26 (schema)Zod schema for scan data input parameters, matching the tool's inputSchema (though registration uses slightly relaxed version without min(1)).const ScanDataSchema = z.object({ id: z.string().min(1), eventType: z.string().optional(), });