due_diligence — nordic data MCP Prompt

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

by client

How to invoke due_diligence from your client

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

Other prompts on this server

• vat_check
• sanctions_screening

nordic data also offers 3 resources — 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.