pulsemcp Safe content atomic mcp-remote

Inbound Lead Generation

The Lead Generation Server is a production-grade system built on the MCP Python SDK that enables AI assistants to discover and enrich business leads through multiple data sources. It implements a complete lead lifecycle with UUID-based tracking, leveraging Google CSE for discovery, Hunter.io and Clearbit for data enrichment, and LinkedIn scraping via Playwright for deeper insights. The server features smart caching with Redis, asynchronous processing for high concurrency, and comprehensive monitoring via Prometheus. Particularly valuable for sales teams and marketers who need to generate qualified leads without switching between multiple tools, it provides a unified API for lead generation, enrichment, and maintenance operations.

Cognium trust score

50%

Tier

Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/bashirk/inbound-mcp
Author type: human
Updated: 2026-04-25

View source Find related skills

MCP

Resolve Inbound Lead Generation from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"