
Leadloadz
io.github.Ali1041Published by GitHub account Ali1041v1.1.3Updated Oct 24, 2026
B2B lead search and email verification MCP server
Overview
Lets an assistant search indexed B2B contacts, verify email deliverability, and check Leadloadz account usage quotas.
- What you can do
- Connects an AI assistant to the Leadloadz B2B lead generation platform over stdio. It exposes three tools: search_leads finds indexed B2B contacts by role, company, location, or technology using natural-language queries and returns leads with deliverability scores; verify_email checks an address in real time and returns a deliverability score and risk assessment; get_user_stats reads usage counters such as searches performed, emails verified, and remaining quota.
- When to use it
- Useful when an assistant needs to build or enrich prospect lists, look up contacts matching a target profile, or screen email addresses before outreach. Also handy for checking how much of a Leadloadz plan has been consumed.
- Requirements
- Runs locally as an npm package via npx or a global install, so Node.js is needed. Requires a Leadloadz account and an API key supplied through the LEADLOADZ_API_KEY environment variable; LEADLOADZ_API_BASE, LEADLOADZ_TIMEOUT_MS, and LEADLOADZ_DISABLE_TELEMETRY are optional. Network access to the Leadloadz API is required.
Installation
In SourceWeft
- Open Leadloadz in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@leadloadz/mcp-server
A Model Context Protocol (MCP) server that connects AI assistants to the Leadloadz B2B lead generation platform.
Features
- Search Leads — Find verified B2B leads using natural language queries
- Verify Email — Real-time email verification with deliverability scoring
- Get Stats — Check your usage and remaining quotas
- Interactive Setup — Built-in wizard to get your API key
- Anonymous Telemetry — Helps us improve the product (no PII, opt-out via
LEADLOADZ_DISABLE_TELEMETRY=1)
Quick Start
Don't have an API key yet?
Run the setup wizard:
This will guide you through creating an account and getting your API key.
Already have an API key?
Add it to your MCP client configuration (see below) and start using Leadloadz directly.
Installation
Via npx (recommended)
No installation required. AI clients can run the server directly:
Via npm
Configuration
You need a Leadloadz API key to use this server.
- Sign up at leadloadz.com
- Go to Dashboard → API Tokens
- Generate a new token
- Copy the token value
Claude Desktop
Add to your claude_desktop_config.json:
Cline (VS Code)
Add to your Cline MCP settings:
Other Clients
Any MCP client that supports stdio transport can use:
Environment Variables
Tools
search_leads
Search indexed B2B contacts by role, company, location, or technology.
Parameters:
query(string, required): Specific natural-language search querylimit(number, optional): Max results. Default: 10, Cap: 50
Returns: Verified leads with deliverability scores
verify_email
Check email deliverability in real-time.
Parameters:
email(string, required): Email address to verify
Returns: Deliverability score and risk assessment
get_user_stats
Read current usage counters.
Returns: Searches performed, emails verified, and remaining quota
Security
- Your API key is never logged or exposed in error messages
- All errors are sanitized to prevent information leakage
- Communication with Leadloadz APIs uses HTTPS
Support
- Website: leadloadz.com
- Issues: GitHub Issues
License
MIT
Source: README.md at commit 6257eca
Tools
0Version history
1- v1.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts