verify_list_status — Getlead MCP Tool
verify_list_status
(verify list status) is one of 35 tools on the
Getlead
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_list_status from your client
- Claude Code Getlead verify_list_status run in your project directory
- Claude Desktop Getlead verify_list_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Getlead verify_list_status ~/.cursor/mcp.json
- VS Code Getlead verify_list_status .vscode/mcp.json
- Zed Getlead verify_list_status ~/.config/zed/settings.json
- Windsurf Getlead verify_list_status ~/.codeium/windsurf/mcp_config.json
- Cline Getlead verify_list_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Getlead verify_list_status ~/.gemini/settings.json
- Grok Getlead verify_list_status .mcp.json (in your project root)
- ChatGPT Getlead verify_list_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Getlead verify_list_status Settings → Connectors → Add custom connector
- LangChain Getlead verify_list_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http leads https://mcp.getle.ad/mcp
Other tools on this server
- get_account
- list_mailboxes
- test_mailbox
- list_campaigns
- get_campaign_stats
- get_campaign_analytics
- control_campaign
- create_campaign
- crm_leads
- crm_update_lead
- check_deliverability
- suppression
- email_templates
- get_inbox
- get_thread
- draft_reply
- send_reply
- list_opportunities
- update_opportunity
- preview_b2b_leads
- search_b2b_leads
- enrich_lead
- scrape_leads_start
- scrape_job_status
- scrape_job_leads
- verify_email
- verify_list_start
- find_email
- list_lists
- create_list
- get_list_leads
- add_leads_to_list
- export_list_csv
- delete_list
This list was read from the server itself, by connecting to it and calling tools/list on 26 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.