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