get_events — market data MCP Tool Read-only
get_events
(get events) is one of 22 tools on the
market data
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_events from your client
- Claude Code market data get_events run in your project directory
- Claude Desktop market data get_events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor market data get_events ~/.cursor/mcp.json
- VS Code market data get_events .vscode/mcp.json
- Zed market data get_events ~/.config/zed/settings.json
- Windsurf market data get_events ~/.codeium/windsurf/mcp_config.json
- Cline market data get_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI market data get_events ~/.gemini/settings.json
- Grok market data get_events .mcp.json (in your project root)
- ChatGPT market data get_events Settings → Connectors → Advanced → Developer mode
- Claude.ai market data get_events Settings → Connectors → Add custom connector
- LangChain market data get_events pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http market-data https://iturri.ai/mcpOther tools on this server
- describe_catalog
- get_bars
- get_features
- build_bundle
- get_regime_label
- get_funding
- get_open_interest
- get_long_short
- get_context
- get_orderflow
- validate_backtest_data
- audit_my_data
- lookahead_check
- survivorship_check
- get_fundamentals
- get_insider
- get_institutional
- get_funding_spread
- get_market_pulse
- get_whats_new
- get_quality_receipts
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.