Skip to main content
Glama

spiderfoot_scan_info

Retrieve metadata and configuration details for a specific SpiderFoot OSINT reconnaissance scan using its unique scan ID.

Instructions

Retrieve scan metadata/config for a scan ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • src/index.ts:63-67 (registration)
    Registration of the 'spiderfoot_scan_info' MCP tool, including inline input schema (id: string) and handler function that calls sf.scanInfo(id) and returns JSON response.
    server.registerTool( 'spiderfoot_scan_info', { title: 'Scan Info', description: 'Retrieve scan metadata/config for a scan ID.', inputSchema: { id: z.string() } }, async ({ id }) => ({ content: [{ type: 'text', text: JSON.stringify(await sf.scanInfo(id)) }] }) );
  • Registration of the 'spiderfoot_scan_info' MCP tool in HTTP server variant, including inline input schema (id: string) and handler function that calls sf.scanInfo(id) and returns JSON response.
    server.registerTool( 'spiderfoot_scan_info', { title: 'Scan Info', description: 'Retrieve scan metadata/config for a scan ID.', inputSchema: { id: z.string() } }, async ({ id }) => ({ content: [{ type: 'text', text: JSON.stringify(await sf.scanInfo(id)) }] }) );
  • Core handler logic for retrieving scan information: HTTP GET to /scanopts endpoint with scan ID parameter, returning the response data.
    async scanInfo(id: string) { const { data } = await this.http.get('/scanopts', { params: { id } }); return data; }
  • Zod schema for scan info input parameters (id: non-empty string), defined but not directly used in tool registration.
    const ScanInfoSchema = z.object({ id: z.string().min(1) });

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