LeadMCP
ai.leadmcpPublished by leadmcp.aiOfficial publisherv1.0.0Updated Oct 24, 2026
B2B contact database for AI agents: search, count, export and enrich 375M+ contacts.
Overview
Lets an assistant search, count, export, and enrich B2B contacts from a large business contact database.
- What you can do
- LeadMCP is a remote MCP server that gives an assistant access to a B2B contact database described as containing over 375 million contacts. According to its description, the assistant can search contacts, count matching records, export them, and enrich existing contact data. It is a hosted endpoint rather than a local package, so the assistant connects to it over the network.
- When to use it
- Use it when an assistant needs to look up business contacts, size a prospect list, pull contact records for outreach or research, or add missing details to existing contact data. It fits sales, marketing, and recruiting workflows that depend on B2B contact information.
- Requirements
- A remote MCP connection to the provider's hosted endpoint over streamable HTTP. Authentication is OAuth and is required, so the user must complete an OAuth sign-in with the provider. No environment variables or headers are declared, and no local runtime or package is needed.
Installation
In SourceWeft
- Open LeadMCP in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.leadmcp%2Fleadmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"leadmcp": {
"type": "http",
"url": "https://mcp.leadmcp.ai/"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 12, 2026
Score
67% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.