BE-Lead-Hunter
Pricing
Pay per usage
US city/category business discovery, bounded public website contacts and CSV/JSON/dataset exports. Fresh research needs explicit opt-ins and run cost limits. No mailbox verification, AI or sending. Standalone per-run storage; optional database modes remain separate.
Connect the BE-Lead-Hunter Actor to an AI application through the Apify MCP server. MCP clients with OAuth support sign you in to Apify without an API token.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,wooden_turbojet/be-lead-hunter" } }}Add the configuration above to your project's .mcp.json file for Claude Code, then run /mcp in Claude Code to sign in to Apify. It connects to the hosted Apify MCP server with the BE-Lead-Hunter Actor already loaded. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
For other MCP clients, get a client-specific configuration with the BE-Lead-Hunter Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,wooden_turbojet/be-lead-hunter.
You can connect to the Apify MCP server using an MCP client that supports Streamable HTTP.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.