get_job_status — Verifly MCP Tool Read-only

get_job_status (get job status) is one of 17 tools on the Verifly MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call get_job_status from your client

Claude Code Verifly get_job_status run in your project directory
Claude Desktop Verifly get_job_status ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Verifly get_job_status ~/.cursor/mcp.json
VS Code Verifly get_job_status .vscode/mcp.json
Zed Verifly get_job_status ~/.config/zed/settings.json
Windsurf Verifly get_job_status ~/.codeium/windsurf/mcp_config.json
Cline Verifly get_job_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Verifly get_job_status ~/.gemini/settings.json
Grok Verifly get_job_status .mcp.json (in your project root)
ChatGPT Verifly get_job_status Settings → Connectors → Advanced → Developer mode
Claude.ai Verifly get_job_status Settings → Connectors → Add custom connector
LangChain Verifly get_job_status pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http verifly https://verifly.email/mcp

Other tools on this server

get_started
verify_email_demo
verify_email
verify_batch
clean_email_list
extract_emails
check_domain_health
get_credits
submit_bulk
get_job_results
list_jobs
get_usage
get_account
get_packages
buy_credits
register_account

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.

Verifly MCP server