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