get_feedback_reply — Crypto Due Diligence MCP Tool Read-only
get_feedback_reply
(get feedback reply) is one of 4 tools on the
Crypto Due Diligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_feedback_reply from your client
- Claude Code Crypto Due Diligence get_feedback_reply run in your project directory
- Claude Desktop Crypto Due Diligence get_feedback_reply ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Crypto Due Diligence get_feedback_reply ~/.cursor/mcp.json
- VS Code Crypto Due Diligence get_feedback_reply .vscode/mcp.json
- Zed Crypto Due Diligence get_feedback_reply ~/.config/zed/settings.json
- Windsurf Crypto Due Diligence get_feedback_reply ~/.codeium/windsurf/mcp_config.json
- Cline Crypto Due Diligence get_feedback_reply ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Crypto Due Diligence get_feedback_reply ~/.gemini/settings.json
- Grok Crypto Due Diligence get_feedback_reply .mcp.json (in your project root)
- ChatGPT Crypto Due Diligence get_feedback_reply Settings → Connectors → Advanced → Developer mode
- Claude.ai Crypto Due Diligence get_feedback_reply Settings → Connectors → Add custom connector
- LangChain Crypto Due Diligence get_feedback_reply pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cryptodd https://cryptodd.openkrill.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 16 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.