track_record — HillSignal MCP Tool
track_record
(track record) is one of 24 tools on the
HillSignal
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call track_record from your client
- Claude Code HillSignal track_record run in your project directory
- Claude Desktop HillSignal track_record ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HillSignal track_record ~/.cursor/mcp.json
- VS Code HillSignal track_record .vscode/mcp.json
- Zed HillSignal track_record ~/.config/zed/settings.json
- Windsurf HillSignal track_record ~/.codeium/windsurf/mcp_config.json
- Cline HillSignal track_record ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HillSignal track_record ~/.gemini/settings.json
- Grok HillSignal track_record .mcp.json (in your project root)
- ChatGPT HillSignal track_record Settings → Connectors → Advanced → Developer mode
- Claude.ai HillSignal track_record Settings → Connectors → Add custom connector
- LangChain HillSignal track_record pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hillsignalapp https://www.hillsignal.com/api/mcpOther tools on this server
- resolve_entity
- get_entity
- search_awards
- award_totals
- search_opportunities
- congressional_trades
- get_politician
- insider_trades
- search_bills
- executive_orders
- pac_lookup
- pac_totals
- lobbying
- money_trail
- super_pacs
- outside_money
- data_coverage
- list_themes
- get_theme
- latest_events
- institutional_holders
- foreign_agents
- form_d_raises
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.