cot_positioning — XOOMAR market data MCP Tool
cot_positioning
(cot positioning) is one of 26 tools on the
XOOMAR market data
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call cot_positioning from your client
- Claude Code XOOMAR market data cot_positioning run in your project directory
- Claude Desktop XOOMAR market data cot_positioning ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor XOOMAR market data cot_positioning ~/.cursor/mcp.json
- VS Code XOOMAR market data cot_positioning .vscode/mcp.json
- Zed XOOMAR market data cot_positioning ~/.config/zed/settings.json
- Windsurf XOOMAR market data cot_positioning ~/.codeium/windsurf/mcp_config.json
- Cline XOOMAR market data cot_positioning ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI XOOMAR market data cot_positioning ~/.gemini/settings.json
- Grok XOOMAR market data cot_positioning .mcp.json (in your project root)
- ChatGPT XOOMAR market data cot_positioning Settings → Connectors → Advanced → Developer mode
- Claude.ai XOOMAR market data cot_positioning Settings → Connectors → Add custom connector
- LangChain XOOMAR market data cot_positioning pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http xoomar-mcp https://xoomar.com/mcp
Other tools on this server
- short_interest
- short_volume
- fails_to_deliver
- insider_trades
- insider_clusters
- threshold_list
- planned_insider_sales
- large_holders
- fund_holders
- fund_portfolio
- company_financials
- corporate_events
- earnings_calendar
- funding_rates
- fed_liquidity
- policy_rates
- macro_series
- treasury_auctions
- economic_calendar
- private_placements
- ipo_pipeline
- bitcoin_treasuries
- federal_contracts
- crypto_market
- api_reference
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.