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