get_signal_markets — PolySignals.net MCP Tool Read-only
get_signal_markets
(get signal markets) 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_signal_markets from your client
- Claude Code PolySignals.net get_signal_markets run in your project directory
- Claude Desktop PolySignals.net get_signal_markets ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PolySignals.net get_signal_markets ~/.cursor/mcp.json
- VS Code PolySignals.net get_signal_markets .vscode/mcp.json
- Zed PolySignals.net get_signal_markets ~/.config/zed/settings.json
- Windsurf PolySignals.net get_signal_markets ~/.codeium/windsurf/mcp_config.json
- Cline PolySignals.net get_signal_markets ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PolySignals.net get_signal_markets ~/.gemini/settings.json
- Grok PolySignals.net get_signal_markets .mcp.json (in your project root)
- ChatGPT PolySignals.net get_signal_markets Settings → Connectors → Advanced → Developer mode
- Claude.ai PolySignals.net get_signal_markets Settings → Connectors → Add custom connector
- LangChain PolySignals.net get_signal_markets 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.