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