screening_dispute — axion gateway MCP Tool
screening_dispute
(screening dispute) is one of 11 tools on the
axion gateway
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call screening_dispute from your client
- Claude Code axion gateway screening_dispute run in your project directory
- Claude Desktop axion gateway screening_dispute ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor axion gateway screening_dispute ~/.cursor/mcp.json
- VS Code axion gateway screening_dispute .vscode/mcp.json
- Zed axion gateway screening_dispute ~/.config/zed/settings.json
- Windsurf axion gateway screening_dispute ~/.codeium/windsurf/mcp_config.json
- Cline axion gateway screening_dispute ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI axion gateway screening_dispute ~/.gemini/settings.json
- Grok axion gateway screening_dispute .mcp.json (in your project root)
- ChatGPT axion gateway screening_dispute Settings → Connectors → Advanced → Developer mode
- Claude.ai axion gateway screening_dispute Settings → Connectors → Add custom connector
- LangChain axion gateway screening_dispute pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http axion-gateway https://mcp.getaxionlabs.com/mcpOther tools on this server
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.