Lead411

io.github.kunal-lead411Published by GitHub account kunal-lead411v1.0.0Updated Oct 24, 2026

B2B lead generation, company search, and contact enrichment from Lead411.

VerifiedSSEWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search B2B companies and contacts and enrich lead data through the Lead411 platform.

What you can do
Lead411 is a remote MCP server that connects an assistant to Lead411's B2B data platform. Based on the description, it supports lead generation, company search and contact enrichment, so an assistant can look up businesses and people and fill in details on contacts. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to research prospective business customers, find companies matching certain criteria, or enrich existing contact records with Lead411 data during sales or marketing work.
Requirements
A remote MCP connection to the Lead411 endpoint over SSE. A Lead411 account and API key are required, supplied in the X-API-KEY header. Network access to the Lead411 service is needed.
Before you install
The server requires a Lead411 API key in the X-API-KEY header; treat it as a secret and check what plan or usage limits apply. Queries and enrichment requests send company and contact data to Lead411, a third party, so consider privacy and data-handling obligations before use.

Installation

In SourceWeft

  1. Open Lead411 in the dashboard and add it to a workspace.
  2. Connect X-API-KEY credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via SSE. 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/io.github.kunal-lead411%2Flead411/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lead411": {
      "type": "sse",
      "url": "https://mcp.lead411.com/",
      "headers": {
        "X-API-KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 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 listedRequired15 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.