DetectRugSignals — EchoLedger MCP Tool
DetectRugSignals
(detect rug signals) is one of 11 tools on the
EchoLedger
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call DetectRugSignals from your client
- Claude Code EchoLedger DetectRugSignals run in your project directory
- Claude Desktop EchoLedger DetectRugSignals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EchoLedger DetectRugSignals ~/.cursor/mcp.json
- VS Code EchoLedger DetectRugSignals .vscode/mcp.json
- Zed EchoLedger DetectRugSignals ~/.config/zed/settings.json
- Windsurf EchoLedger DetectRugSignals ~/.codeium/windsurf/mcp_config.json
- Cline EchoLedger DetectRugSignals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EchoLedger DetectRugSignals ~/.gemini/settings.json
- Grok EchoLedger DetectRugSignals .mcp.json (in your project root)
- ChatGPT EchoLedger DetectRugSignals Settings → Connectors → Advanced → Developer mode
- Claude.ai EchoLedger DetectRugSignals Settings → Connectors → Add custom connector
- LangChain EchoLedger DetectRugSignals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http echoledger-mcp https://mcp.echoledger.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.