What it does
The server exposes three tools. search_leads finds B2B contacts by role, company, location or technology from a natural-language query, returning up to 50 results (10 by default). verify_email checks an address's deliverability in real time and returns a score and risk assessment. get_user_stats reports searches performed, emails verified and remaining quota.
It suits AI assistant workflows that need B2B contact lookups or email checks through Leadloadz. Users without an account can run a built-in setup wizard that guides them through signing up and obtaining an API key.
A Leadloadz API key is required, created under Dashboard, API Tokens after signing up. The server runs through npx or npm and is added to an MCP client configuration such as Claude Desktop or Cline, using stdio transport. LEADLOADZ_API_KEY is mandatory; the API base URL, a request timeout (default 30000 ms) and an opt-out for anonymous telemetry are optional. The publisher states that the API key is never logged and that errors are sanitised, and that communication uses HTTPS.
Limitations and requirements
Requires a Leadloadz account and API key. Search results are capped at 50 per request. Usage is limited by the account's remaining quota. The API base URL should not use the www subdomain, because redirects strip authentication headers.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.Ali1041/leadloadz
B2B lead search and email verification MCP server
v1.1.3As shown on registry.modelcontextprotocol.io when we last read it