Nose for Leads MCP MCP server

An official MCP server that allows AI agents to automate local business lead generation. It discovers businesses based on plain-English descriptions, verifies email addresses via live tests, and returns validated leads with detailed receipts, enabling end-to-end outreach campaigns without manual intervention.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Nose for Leads

MCP endpoint (Streamable HTTP)

https://api.noseforleads.com/mcp

Vendor documentation

What you can do with it

Translate plain-English target descriptions into structured queries
Start and monitor automated lead discovery and verification campaigns
Fetch validated leads and detailed rejection receipts
Manage campaign credits and suppression lists

Tools advertised by the last live check:

translate_icp
start_campaign
get_campaign_status
fetch_results
get_icp_pack
add_suppression
review_lead
get_credits
list_campaigns
get_usage
send_feedback

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http nose-for-leads-mcp https://api.noseforleads.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add nose-for-leads-mcp --url https://api.noseforleads.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable nose-for-leads-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "nose-for-leads-mcp": {
      "url": "https://api.noseforleads.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "nose-for-leads-mcp": {
      "type": "streamableHttp",
      "url": "https://api.noseforleads.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start nose-for-leads-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "nose-for-leads-mcp": {
      "type": "http",
      "url": "https://api.noseforleads.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http nose-for-leads-mcp https://api.noseforleads.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "nose-for-leads-mcp": {
      "url": "https://api.noseforleads.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "nose-for-leads-mcp": {
      "serverUrl": "https://api.noseforleads.com/mcp"
    }
  }
}

See all 347

Do you run Nose for Leads MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing