Leadsmarts

app.leadsmartsPublished by leadsmarts.appOfficial publisherv3.1.0Updated Oct 24, 2026

Qualify B2B leads: live-web research, Hot/Warm/Cold verdicts with evidence, and outreach drafts.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

LeadSmarts is a remote MCP server that lets an assistant research B2B leads on the live web, score them Hot/Warm/Cold with evidence, and draft outreach.

What you can do
  • Research B2B leads using live-web information
  • Return qualification verdicts (Hot, Warm or Cold) with supporting evidence
  • Draft outreach messages for the leads it evaluates
  • No tool list is published, so exact operations are not documented; capabilities are inferred from the registry description.
When to use it
Useful when a sales or growth workflow needs quick, evidence-backed qualification of B2B prospects and starting drafts for outreach, without leaving the assistant.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. Requires a LeadSmarts API key (lsk_...) sent in the Authorization header, created under API & agents in the LeadSmarts app. A LeadSmarts account is implied.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared transcripts. Outreach drafts and lead verdicts are generated content and should be reviewed before sending. The server performs live-web research, so prospect data is sent to LeadSmarts and third-party web sources.

Installation

In SourceWeft

  1. Open Leadsmarts in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/app.leadsmarts%2Fleadsmarts/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": {
    "leadsmarts": {
      "type": "http",
      "url": "https://mcp.leadsmarts.app/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v3.1.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

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