Lead Radar

fr.lead-radarPublished by lead-radar.frOfficial publisherv1.0.0Updated Oct 24, 2026

B2B lead generation from Google Maps: search, dedupe and email-enrich businesses. Needs API key.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant generate B2B leads from Google Maps by searching, deduplicating and email-enriching businesses.

What you can do
Lead Radar is a remote MCP server for B2B lead generation built on Google Maps data. According to the registry description, it lets an assistant search for businesses, remove duplicates across results, and enrich them with email addresses. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to build or clean up prospect lists of local businesses, for example for outbound sales or market research, and you want search, deduplication and email enrichment in one step.
Requirements
A remote endpoint at lead-radar.fr over streamable HTTP. Authentication is required via OAuth, with an API key sent in the Authorization header as a bearer token (a value beginning with lr_). No local runtime or packages are needed.
Before you install
The server requires an API key in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configurations. Email enrichment returns contact data about third-party businesses, so consider privacy and outreach rules before using it. The manifest lists no tools, so what the server reads or writes cannot be verified from this listing.

Installation

In SourceWeft

  1. Open Lead Radar in the dashboard and add it to a workspace.
  2. Connect the required 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 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/fr.lead-radar%2Flead-radar/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lead-radar": {
      "type": "http",
      "url": "https://lead-radar.fr/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

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 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.