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