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