Lead Generation MCP Server

Five tools for MCP clients: public business contacts, target-company hiring signals, building permits, Amazon product research, and Perplexity brand checks. Each tool calls the matching samstorm Actor and returns its structured records. Source coverage, costs and limitations of the underlying Actor apply.

Start with a small call

Connect an MCP client that supports Streamable HTTP to the authenticated Apify Standby endpoint shown for this Actor, with /mcp as the path. Follow your client's remote-server authentication settings and Apify's displayed connection instructions. Keep your Apify token private. This server is designed for Apify Standby; it is not a batch scraper or a generic REST endpoint.

Try find_business_leads with:

{ "businessType": "Med Spa", "location": "Miami, FL", "maxResults": 3 }

Review the returned source links and contact evidence before increasing volume. A missing email is not a confirmed invalid mailbox, and SMTP confirmation is not a delivery guarantee.

Tools

find_business_leads

businessType supports Dentist, Med Spa, Restaurant, Contractor, Lawyer, Real Estate Agent, Auto Dealer, Wedding Vendor, and Financial Advisor. Supply location and maxResults (1–100, default 10). Lawyer searches use a general lawyer query; use the dedicated Lawyer Actor for practice-area filters, multi-city input and exclusions. Other niches use the underlying Actor's default category.

find_hiring_companies

Supply 1–20 public Greenhouse or Lever jobBoards URLs, plus optional jobTitle and location words. Objects with url, companyName and companyWebsite are also accepted. Employer websites must be supplied for optional email extraction; none are guessed. maxResults caps company records, with at most one matching company per board. A vacancy indicates hiring activity, not proof of purchase intent or a decision-maker's identity.

{
  "jobBoards": [
    { "url": "https://job-boards.greenhouse.io/greenhouse", "companyName": "Greenhouse" },
    { "url": "https://jobs.lever.co/spotify", "companyName": "Spotify" }
  ],
  "jobTitle": "Engineer",
  "location": "",
  "maxResults": 2
}

This is target-company monitoring, not whole-web discovery. If jobBoards is omitted, the legacy Google Jobs path requires jobTitle and location and remains unreliable. No paid provider API key is needed for public-board mode.

find_building_permits

city supports chicago, los_angeles, nyc, austin, seattle and san_francisco. permitType supports all, roofing, hvac, plumbing, electrical, remodel and new_construction. maxResults is 1–100, default 20. The child searches the last 30 days; city-source freshness and keyword matching affect results. A permit does not establish that a property owner wants outreach.

research_amazon_products

Supply 1–100 asins and a supported marketplace (amazon.com by default). Product availability varies; unavailable price, rank, rating or seller metrics remain null. Start with one ASIN that currently has a public product page.

monitor_brand_in_ai

Supply brands, prompts, and a required perplexityApiKey. Each list accepts 1–100 non-empty strings. Format a brand as Brand Name (domain.com) for citation matching. Use your own funded Perplexity key: provider token and request charges go to your Perplexity account. The actor author provides no shared key or API credits. Keep keys out of shared transcripts, public examples and support issues. If your MCP client cannot handle credentials privately, use the dedicated Perplexity Actor's secret input instead.

Pricing and limits

The configured MCP result fee is $10 per 1,000 returned records ($0.01 each). Three returned records therefore incur $0.03 in MCP result fees, plus underlying Actor fees, platform usage and any external provider charges. The Pricing tab is authoritative and can reflect plan discounts. This is a per-record fee, not a flat call fee. Failed or empty child calls do not create MCP result records, but incurred platform or provider usage can still be charged.

Each child run has a 300-second runtime limit and a $1 maximum Actor-event-charge setting. That setting does not cap all possible platform or external API costs. Large requested outputs may be limited by the charge cap. Calls report failed/unfinished child runs as errors, with their run ID; inspect partial child output before retrying. Up to 10,000 child records can be returned by a call. Confirm that your Apify plan and Actor permissions support actor-to-actor calls.

Successful child results are saved in this MCP run's dataset and returned to the client. Empty results can be legitimate; extraction failures are separate errors. Availability of an email or source field varies by record.

Dedicated Actors and samples

• Lawyer leads: practice areas, multi-city research and previous-listing exclusions.
• Dentist leads: dental and healthcare practice research.
• Med Spa leads: med spas and aesthetics business contacts.
• Hiring Intent: public company boards and source evidence.
• Perplexity brand monitoring: customer-funded API access with secret input.

For help, open an issue with a current run link, tool name and non-sensitive reproduction input. Do not include tokens, API keys or private customer data. End-to-end behavior depends on your MCP client, authentication, Apify plan and underlying sources.