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