company_due_diligence — Signal8 MCP Prompt

company_due_diligence is one of 3 prompts on the Signal8 MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke company_due_diligence from your client

• Claude Code Signal8 Prompt/company_due_diligence run in your project directory
• Claude Desktop Signal8 Prompt/company_due_diligence ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Signal8 Prompt/company_due_diligence ~/.cursor/mcp.json
• VS Code Signal8 Prompt/company_due_diligence .vscode/mcp.json
• Zed Signal8 Prompt/company_due_diligence ~/.config/zed/settings.json
• Windsurf Signal8 Prompt/company_due_diligence ~/.codeium/windsurf/mcp_config.json
• Cline Signal8 Prompt/company_due_diligence ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Signal8 Prompt/company_due_diligence ~/.gemini/settings.json
• Grok Signal8 Prompt/company_due_diligence .mcp.json (in your project root)
• ChatGPT Signal8 Prompt/company_due_diligence Settings → Connectors → Advanced → Developer mode
• Claude.ai Signal8 Prompt/company_due_diligence Settings → Connectors → Add custom connector
• LangChain Signal8 Prompt/company_due_diligence pip install langchain-mcp-adapters

Other prompts on this server

• screening_workflow
• institutional_analysis

Signal8 also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.