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