list_supported_chains — cryptopulse MCP Tool Read-only
list_supported_chains
(list supported chains) is one of 7 tools on the
cryptopulse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_supported_chains from your client
- Claude Code cryptopulse list_supported_chains run in your project directory
- Claude Desktop cryptopulse list_supported_chains ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor cryptopulse list_supported_chains ~/.cursor/mcp.json
- VS Code cryptopulse list_supported_chains .vscode/mcp.json
- Zed cryptopulse list_supported_chains ~/.config/zed/settings.json
- Windsurf cryptopulse list_supported_chains ~/.codeium/windsurf/mcp_config.json
- Cline cryptopulse list_supported_chains ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI cryptopulse list_supported_chains ~/.gemini/settings.json
- Grok cryptopulse list_supported_chains .mcp.json (in your project root)
- ChatGPT cryptopulse list_supported_chains Settings → Connectors → Advanced → Developer mode
- Claude.ai cryptopulse list_supported_chains Settings → Connectors → Add custom connector
- LangChain cryptopulse list_supported_chains pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cryptopulse https://cryptopulse.uno/api/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.