Lead data is personal data, and a debug log is where it quietly leaks. Request and response payloads are reduced to non-identifying shape markers by default — you can see that a first name was sent without recording the name — and verbatim logging is an explicit opt-in for a short debugging session.
A minimal MCP server over the Generect Live API for lead generation. Five tools: search leads and companies by ICP filters, pull one lead from a LinkedIn profile URL, generate an email address from a name and a domain, and a health check.
- search_leads filters by job title, industry, location, company name or company link, with limit, offset, max_items and a compact mode
- search_companies filters by keywords, industries, headcounts and company types, and can fall back to deriving companies from lead results
- get_lead_by_url takes a LinkedIn profile URL and can also return posts, comments and people-also-viewed
- generate_email builds an address from a first name, last name and domain
- health runs a quick lead-by-link request to confirm the API is answering
- Every tool accepts timeout_ms, which matters because these searches are slow by nature
The hosted server at https://mcp.generect.com/mcp speaks Streamable HTTP with OAuth 2.1, including dynamic client registration — connect, then paste your Generect API token on the authorization page. Clients that cannot complete OAuth may send the key in an Authorization header instead, including through mcp-remote. For local use: Node 18 or newer with GENERECT_API_BASE, GENERECT_API_KEY, GENERECT_TIMEOUT_MS, JWT_SIGNING_KEY and TOKEN_ENCRYPTION_KEY set. Keys come from beta.generect.com.
One command plus a key — npm i -g generect-ultimate-mcp, then supply credentials