Connect AI agents to verified B2B lead data through the Model Context Protocol. Supports Claude, Cursor, GPT-4, and custom agents.
Configure in 5 minutes. Single API token connects unlimited agents.
Token-based auth with SHA-256 hashing. Rate limited to 30 req/min.
Works with Claude, Cursor, GPT-4, and any MCP-compatible agent.
The Model Context Protocol (MCP) is an open standard developed by Anthropic that enables AI assistants to securely connect to external data sources and tools. Leadloadz provides an MCP server that exposes lead search and email verification as tools your AI agents can call.
Base URL: https://leadloadz.com/api/mcp
Protocol: JSON-RPC 2.0 over HTTP
Authentication: Bearer token in Authorization header
Add to your Claude Desktop config file:
{
"mcpServers": {
"leadloadz": {
"command": "npx",
"args": ["-y", "@leadloadz/mcp-server"],
"env": {
"LEADLOADZ_API_TOKEN": "your-api-token-here"
}
}
}
}Add to Cursor settings (Settings > MCP > Add Server):
Type: HTTP
URL: https://leadloadz.com/api/mcp
Headers:
Authorization: Bearer your-api-token-hereSend JSON-RPC 2.0 requests to the MCP endpoint:
POST https://leadloadz.com/api/mcp
Content-Type: application/json
Authorization: Bearer your-api-token
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}All MCP requests require a valid API token in the Authorization header. Tokens are SHA-256 hashed before storage for security.
Header Format:
Authorization: Bearer <YOUR_API_TOKEN>Getting Your Token
Generate an API token from your dashboard. Free tier includes 1 token. Pro users can create multiple tokens with different scopes.
Search for B2B leads using natural language or structured criteria. Returns verified leads with company info, contact details, and verification status.
| Name | Type | Required | Description |
|---|---|---|---|
| query | string | Yes | Natural language query (e.g., 'CTOs at Series A B2B SaaS in London') |
| limit | number | No | Max results (default: 10, max: 50) |
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_leads",
"arguments": {
"query": "CTOs at Series A B2B SaaS in London",
"limit": 10
}
}
}{
"results": [
{
"name": "Jane Smith",
"title": "CTO",
"company": "TechCorp",
"email": "jane@techcorp.com",
"verified": true,
"location": "London, UK"
}
]
}Verify an email address in real-time. Checks MX records, SMTP deliverability, disposable domains, and role accounts.
| Name | Type | Required | Description |
|---|---|---|---|
| string | Yes | Email address to verify |
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "verify_email",
"arguments": {
"email": "jane@techcorp.com"
}
}
}{
"email": "jane@techcorp.com",
"valid": true,
"mx_valid": true,
"smtp_valid": true,
"disposable": false,
"role_account": false,
"catch_all": false,
"score": 95
}Get the user's current usage statistics including leads found, emails verified, and API usage.
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "get_user_stats",
"arguments": {}
}
}{
"total_leads_found": 247,
"total_emails_verified": 189,
"searches_today": 3,
"exports_today": 15,
"plan": "free"
}curl -X POST https://leadloadz.com/api/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_leads",
"arguments": {
"query": "CTOs at Series A B2B SaaS in London",
"limit": 10
}
}
}'import requests
response = requests.post(
"https://leadloadz.com/api/mcp",
headers={
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
},
json={
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_leads",
"arguments": {
"query": "CTOs at Series A B2B SaaS in London",
"limit": 10
}
}
}
)
results = response.json()
print(results)const response = await fetch("https://leadloadz.com/api/mcp", {
method: "POST",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
},
body: JSON.stringify({
jsonrpc: "2.0",
id: 1,
method: "tools/call",
params: {
name: "search_leads",
arguments: {
query: "CTOs at Series A B2B SaaS in London",
limit: 10
}
}
})
});
const results = await response.json();
console.log(results);The MCP server uses standard JSON-RPC 2.0 error codes with custom extensions for Leadloadz-specific errors.
| Code | Message | Description |
|---|---|---|
| -32700 | Parse error | Invalid JSON was received |
| -32600 | Invalid Request | The JSON sent is not a valid Request object |
| -32601 | Method not found | The method does not exist |
| -32602 | Invalid params | Invalid method parameter(s) |
| -32001 | Authentication failed | Invalid or missing API token |
| -32002 | Rate limit exceeded | 30 requests per minute limit reached |
| -32003 | Insufficient permissions | Token lacks required scopes |
MCP is an open standard developed by Anthropic that enables AI agents to discover and use external tools through a standardized interface. It allows agents to search for leads, verify emails, and access data without custom integration work.
As of 2026, Claude (via Claude Desktop), Cursor (IDE integration), and GPT-4 (with MCP adapters) support MCP. Custom agents using the MCP SDK can also connect.
Sign up for a free Leadloadz account and generate a token from your dashboard. The free tier includes 1 token with 3 searches/day and 50 exports/day.
The MCP server allows 30 requests per minute per user. This includes all tool calls (search_leads, verify_email, get_user_stats).
Yes! Any agent that can send HTTP POST requests with JSON-RPC 2.0 formatting can use the Leadloadz MCP server. See the Custom Agent installation section above.
Yes, the MCP server is included in the free tier. You get 3 lead searches/day, 50 exports/day, and unlimited email verifications.