resolution_diff — Indiana Court Rules MCP Tool
resolution_diff
(resolution diff) is one of 47 tools on the
Indiana Court Rules
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolution_diff from your client
- Claude Code Indiana Court Rules resolution_diff run in your project directory
- Claude Desktop Indiana Court Rules resolution_diff ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Indiana Court Rules resolution_diff ~/.cursor/mcp.json
- VS Code Indiana Court Rules resolution_diff .vscode/mcp.json
- Zed Indiana Court Rules resolution_diff ~/.config/zed/settings.json
- Windsurf Indiana Court Rules resolution_diff ~/.codeium/windsurf/mcp_config.json
- Cline Indiana Court Rules resolution_diff ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Indiana Court Rules resolution_diff ~/.gemini/settings.json
- Grok Indiana Court Rules resolution_diff .mcp.json (in your project root)
- ChatGPT Indiana Court Rules resolution_diff Settings → Connectors → Advanced → Developer mode
- Claude.ai Indiana Court Rules resolution_diff Settings → Connectors → Add custom connector
- LangChain Indiana Court Rules resolution_diff pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http indiana-court-rules https://gateway.pipeworx.io/indiana-court-rules/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
- company_register_search
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- release_calendar_markets
- prediction_calibration
- updown_venue_compare
- updown_divergence_rate
- archive_evidence
- archive_compare
- research_row
- classify_row
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- in_court_rule
- in_court_rules_list
- in_local_rules
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.