Inbound Lead Generation
Rank #13563pulsemcp/bashirk-inbound-lead-generation
Automates lead generation and enrichment by combining Google CSE discovery, Hunter.io and Clearbit data enrichment, and LinkedIn scraping into a unified API with Redis caching and asynchronous processing for high concurrency.
Inbound Lead Generation is a Model Context Protocol (MCP) server published by bashirk. It ranks #13563 of 58,900 servers tracked on MCP Toplist, and its repository has 12 GitHub stars. Inbound Lead Generation is listed on PulseMCP, and ships as a single rolling release with no explicit version metadata. It was first listed on Mar 1, 2025.
Ranks ahead of 45,337 of 58,900 servers on MCP Toplist.
Use Inbound Lead Generation
Inbound Lead Generation doesn’t publish a machine-readable install config. Follow the setup instructions in its repository ↗, or open one of its registry listings above.
Listed on 1 registry
bashirk
Not versioned
This server is published through a registry that does not expose explicit version metadata, and no GitHub release tags were found on the linked repository. The listing tracks a single rolling release.
Frequently asked questions
- What is Inbound Lead Generation?
- Automates lead generation and enrichment by combining Google CSE discovery, Hunter.io and Clearbit data enrichment, and LinkedIn scraping into a unified API with Redis caching and asynchronous processing for high concurrency.
- Who maintains Inbound Lead Generation?
- Inbound Lead Generation is maintained by bashirk, which publishes 1 MCP server (0 total versions) tracked on MCP Toplist.
- Is Inbound Lead Generation an official MCP server?
- Inbound Lead Generation is not on the Official MCP Registry. It is listed on PulseMCP.
- How many versions does Inbound Lead Generation have?
- Inbound Lead Generation ships as a single rolling release with no explicit version metadata.
- Where can I find the source code for Inbound Lead Generation?
- The source code for Inbound Lead Generation is hosted at github.com/bashirk/inbound-mcp.