Skip to main content
Glama
Leadloadz

Leadloadz

by Ali1041

@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)

Related MCP server: leads-mcp

Quick Start

Don't have an API key yet?

Run the setup wizard:

npx @leadloadz/mcp-server --setup

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

No installation required. AI clients can run the server directly:

npx -y @leadloadz/mcp-server

Via npm

npm install -g @leadloadz/mcp-server
leadloadz-mcp

Configuration

You need a Leadloadz API key to use this server.

  1. Sign up at leadloadz.com

  2. Go to Dashboard → API Tokens

  3. Generate a new token

  4. Copy the token value

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "leadloadz": {
      "command": "npx",
      "args": ["-y", "@leadloadz/mcp-server"],
      "env": {
        "LEADLOADZ_API_KEY": "your-api-key-here"
      }
    }
  }
}

Cline (VS Code)

Add to your Cline MCP settings:

{
  "mcpServers": {
    "leadloadz": {
      "command": "npx",
      "args": ["-y", "@leadloadz/mcp-server"],
      "env": {
        "LEADLOADZ_API_KEY": "your-api-key-here"
      }
    }
  }
}

Other Clients

Any MCP client that supports stdio transport can use:

{
  "command": "npx",
  "args": ["-y", "@leadloadz/mcp-server"],
  "env": {
    "LEADLOADZ_API_KEY": "your-api-key-here"
  }
}

Environment Variables

Variable

Required

Default

Description

LEADLOADZ_API_KEY

Yes

—

Your Leadloadz API token

LEADLOADZ_API_BASE

No

https://leadloadz.com/api/mcp

API base URL (do not use www — redirects strip auth headers)

LEADLOADZ_TIMEOUT_MS

No

30000

Request timeout in milliseconds

LEADLOADZ_DISABLE_TELEMETRY

No

0

Set to 1 to disable anonymous usage telemetry

Tools

search_leads

Search indexed B2B contacts by role, company, location, or technology.

Parameters:

  • query (string, required): Specific natural-language search query

  • limit (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

License

MIT

Available Tools

3 tools
get_user_statsA

Read current usage counters: searches performed, emails verified, and remaining quota. Read-only. Requires API key. Rate limit: 30/min per user. Use before batch operations to check available allowance.

Inputs: no named parameters.

search_leadsA

Search indexed B2B contacts by role, company, location, or technology. Read-only; returns verified leads with deliverability scores. Requires API key. Rate limit: 30/min per user. Use verify_email after discovery to confirm deliverability before outreach.

Inputs: query (required), limit.

verify_emailA

Check email deliverability in real-time: MX records, SMTP, disposable/role detection. Read-only. Requires API key. Rate limit: 30/min per user. Use after search_leads or before sending campaigns. Returns deliverability score and risk assessment.

Inputs: email (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: usage stats, lead searching, and email verification. No functional overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_user_stats, search_leads, verify_email).

    Tool Count5/5

    Three tools is well-scoped for a lead generation and verification service, covering essential operations without redundancy.

    Completeness5/5

    The set covers the full workflow: check quota, search leads, and verify email deliverability. No missing critical operations given the read-only nature.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      B2B lead generation MCP server with 20+ lead generation tools - Apollo scraping, Google Maps, email finder, email validator, mobile finder, skip trace, ecommerce store data, and more.
      25
      1,529 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Lead generation MCP server for AI agents. Find emails, verify contacts, enrich profiles, and search prospects using Hunter.io, Apollo.io, and Abstract API.
      8
      16 npm
      MIT