explain_rule — e-Invoice Validator MCP Tool
explain_rule
(explain rule) is one of 3 tools on the
e-Invoice Validator
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call explain_rule from your client
- Claude Code e-Invoice Validator explain_rule run in your project directory
- Claude Desktop e-Invoice Validator explain_rule ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor e-Invoice Validator explain_rule ~/.cursor/mcp.json
- VS Code e-Invoice Validator explain_rule .vscode/mcp.json
- Zed e-Invoice Validator explain_rule ~/.config/zed/settings.json
- Windsurf e-Invoice Validator explain_rule ~/.codeium/windsurf/mcp_config.json
- Cline e-Invoice Validator explain_rule ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI e-Invoice Validator explain_rule ~/.gemini/settings.json
- Grok e-Invoice Validator explain_rule .mcp.json (in your project root)
- ChatGPT e-Invoice Validator explain_rule Settings → Connectors → Advanced → Developer mode
- Claude.ai e-Invoice Validator explain_rule Settings → Connectors → Add custom connector
- LangChain e-Invoice Validator explain_rule pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http einvoice-validator https://einvoice.alexhub.uk/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 23 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.