get_task_status — BillionVerify MCP Tool Read-only
get_task_status
(get task status) 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_task_status from your client
- Claude Code BillionVerify get_task_status run in your project directory
- Claude Desktop BillionVerify get_task_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BillionVerify get_task_status ~/.cursor/mcp.json
- VS Code BillionVerify get_task_status .vscode/mcp.json
- Zed BillionVerify get_task_status ~/.config/zed/settings.json
- Windsurf BillionVerify get_task_status ~/.codeium/windsurf/mcp_config.json
- Cline BillionVerify get_task_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BillionVerify get_task_status ~/.gemini/settings.json
- Grok BillionVerify get_task_status .mcp.json (in your project root)
- ChatGPT BillionVerify get_task_status Settings → Connectors → Advanced → Developer mode
- Claude.ai BillionVerify get_task_status Settings → Connectors → Add custom connector
- LangChain BillionVerify get_task_status 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.