Leadsapp

com.leadsappPublished by leadsapp.comOfficial publisherv1.0.0Updated Oct 24, 2026

Search 136M+ US/CA B2B contacts free, verify emails free, get compliance verdicts. Pay per reveal.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search a large US/Canada B2B contact database, verify emails, and check compliance verdicts, with paid reveals.

What you can do
Connects an assistant to a remote B2B contact service covering US and Canadian business contacts. It supports searching that contact data, verifying email addresses, and retrieving compliance verdicts. Revealing contact details is billed per reveal.
When to use it
Useful when an assistant needs to look up business contacts, check whether an email address is valid, or get a compliance verdict during sales, recruiting, or outreach research. Less relevant if you do not work with B2B contact data.
Requirements
A remote MCP endpoint at the provider's site; no local package or runtime. Requires an API key sent as an Authorization header in the form Bearer la_live_..., obtainable by signing up for a free key. Network access to the provider is needed.
Before you install
The Authorization header carries a live API key, so treat it as a secret and avoid exposing it in logs or shared configs. Revealing contact details costs money on a pay-per-reveal basis, so spending can accumulate. Contact lookups send queries to a third-party service.

Installation

In SourceWeft

  1. Open Leadsapp 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/com.leadsapp%2Fleadsapp/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": {
    "leadsapp": {
      "type": "http",
      "url": "https://leadsapp.com/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.