FlashLeads MCP Server
Related Servers
Alternatives to FlashLeads MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve B2B leads and company data from the LeadBrew database, including contact details and company information.51MIT

Prospeo MCP Serverofficial
AlicenseAqualityFmaintenanceEnables AI tools to search and enrich B2B leads, including finding professional emails, company profiles, and filtering people and companies by various criteria.5343 npmMIT- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search, enrich, and score B2B leads in real time from a database of 10M+ companies.-

Scrupp MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to export leads from LinkedIn, Sales Navigator, and Apollo searches, enrich profiles, look up companies, find decision makers, and discover or verify work emails without writing HTTP calls.MIT- AlicenseNot gradedqualityDmaintenanceGives AI assistants the power to find verified emails, phone numbers, and rich contact data from 575M+ professionals across 30M+ companies via GrowthToolkit's API.MIT

Lusha MCP Pluginofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to find and enrich B2B contacts and companies with verified contact details and buying signals using Lusha's API.4MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_web_harvest_leads retrieves collected lead data, get_web_harvest_status checks agent status and counts, and run_web_harvest initiates or updates the harvesting process. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_web_harvest_leads, get_web_harvest_status, run_web_harvest). The naming is predictable and readable, using clear verbs like 'get' and 'run' paired with descriptive nouns.
With only 3 tools, the set feels thin for a web harvesting domain, as it lacks operations like updating or deleting leads, managing agent configurations, or filtering/searching through collected data. While the core functions are present, the scope is limited, which might require workarounds for more complex tasks.
The tools cover the basic lifecycle of web harvesting: initiating (run_web_harvest), monitoring (get_web_harvest_status), and retrieving results (get_web_harvest_leads). However, there are notable gaps, such as no ability to modify or delete leads, control agent settings, or perform advanced queries on the collected data, which could limit agent effectiveness in extended workflows.