get_split_history — SplitScanner MCP Tool Read-only
get_split_history
(get split history) is one of 23 tools on the
SplitScanner
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_split_history from your client
- Claude Code SplitScanner get_split_history run in your project directory
- Claude Desktop SplitScanner get_split_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SplitScanner get_split_history ~/.cursor/mcp.json
- VS Code SplitScanner get_split_history .vscode/mcp.json
- Zed SplitScanner get_split_history ~/.config/zed/settings.json
- Windsurf SplitScanner get_split_history ~/.codeium/windsurf/mcp_config.json
- Cline SplitScanner get_split_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SplitScanner get_split_history ~/.gemini/settings.json
- Grok SplitScanner get_split_history .mcp.json (in your project root)
- ChatGPT SplitScanner get_split_history Settings → Connectors → Advanced → Developer mode
- Claude.ai SplitScanner get_split_history Settings → Connectors → Add custom connector
- LangChain SplitScanner get_split_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.splitscanner.com/mcpOther tools on this server
- search_companies
- get_company_profile
- get_quote
- get_float
- get_float_history
- search_sec_filings
- get_filing_documents
- get_filing_document
- get_filing_exhibits
- get_exhibit_content
- search_filing_text
- lookup_accession_number
- get_compliance
- get_split_performance
- get_upcoming_reverse_splits
- get_reverse_split_lifecycle
- get_ended_reverse_splits
- get_reverse_split_authority
- get_reverse_splits_list
- search_learn_guides
- get_learn_guide
- define_term
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 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.