Home / MCP registry index / ad.getle/leads
Getlead
ad.getle/leads in the official MCP registry.
Endpoint https://mcp.getle.ad/mcp. Source: github.com/Adgrowofficial/getlead-mcp.
The registry describes it as: Find B2B leads with verified work emails, find and verify emails, and run cold email outreach.
We read its 35 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
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 verify_list_status find_email list_lists create_list get_list_leads add_leads_to_list export_list_csv delete_list
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ad-getle-leads)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.