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