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