Leadloadz
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEADLOADZ_API_KEY | Yes | ||
| LEADLOADZ_API_BASE | No | ||
| LEADLOADZ_TIMEOUT_MS | No |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_leads | 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. |
| verify_email | 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. |
| get_user_stats | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Ali1041/leadloadz-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server