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