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