explain_dilution — DilutionScan MCP Prompt
explain_dilution
is one of 1 prompt on the
DilutionScan
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke explain_dilution from your client
- Claude Code DilutionScan Prompt/explain_dilution run in your project directory
- Claude Desktop DilutionScan Prompt/explain_dilution ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DilutionScan Prompt/explain_dilution ~/.cursor/mcp.json
- VS Code DilutionScan Prompt/explain_dilution .vscode/mcp.json
- Zed DilutionScan Prompt/explain_dilution ~/.config/zed/settings.json
- Windsurf DilutionScan Prompt/explain_dilution ~/.codeium/windsurf/mcp_config.json
- Cline DilutionScan Prompt/explain_dilution ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DilutionScan Prompt/explain_dilution ~/.gemini/settings.json
- Grok DilutionScan Prompt/explain_dilution .mcp.json (in your project root)
- ChatGPT DilutionScan Prompt/explain_dilution Settings → Connectors → Advanced → Developer mode
- Claude.ai DilutionScan Prompt/explain_dilution Settings → Connectors → Add custom connector
- LangChain DilutionScan Prompt/explain_dilution pip install langchain-mcp-adapters
Read from the server itself, by connecting to it and calling prompts/list on 11 November 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.