get_crypto_market — Crypto MCP Tool Read-only
get_crypto_market
(get crypto market) is one of 41 tools on the
Crypto
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_crypto_market from your client
- Claude Code Crypto get_crypto_market run in your project directory
- Claude Desktop Crypto get_crypto_market ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Crypto get_crypto_market ~/.cursor/mcp.json
- VS Code Crypto get_crypto_market .vscode/mcp.json
- Zed Crypto get_crypto_market ~/.config/zed/settings.json
- Windsurf Crypto get_crypto_market ~/.codeium/windsurf/mcp_config.json
- Cline Crypto get_crypto_market ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Crypto get_crypto_market ~/.gemini/settings.json
- Grok Crypto get_crypto_market .mcp.json (in your project root)
- ChatGPT Crypto get_crypto_market Settings → Connectors → Advanced → Developer mode
- Claude.ai Crypto get_crypto_market Settings → Connectors → Add custom connector
- LangChain Crypto get_crypto_market pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crypto https://gateway.pipeworx.io/crypto/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- get_crypto_price
- get_crypto_history
- get_crypto_global
- get_exchange_rate
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.