LeadSpark MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token for higher API rate limits | |
| HUNTER_API_KEY | No | Hunter.io API key for email verification |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| research_companyA | Research a company by domain or name. Returns company info, tech stack, social links, hosting, email provider, and more. Aggregates data from website scraping, DNS, SSL certificates, GitHub, and DuckDuckGo. |
| find_contactsA | Find key people at a company. Scrapes team/about pages for names, titles, and LinkedIn URLs. Generates probable email addresses using common patterns. |
| lookup_tech_stackA | Detect technologies used on a website. Identifies CMS, frameworks, analytics, CDN, hosting, chat tools, payment processors, and more from HTML, headers, and meta tags. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
research_company and lookup_tech_stack overlap significantly because research_company already returns tech stack, hosting, and email provider information. find_contacts is clearly distinct, but an agent could easily hesitate between the two company-research tools.
All tool names follow a consistent verb_noun pattern using lowercase snake_case: research_company, find_contacts, lookup_tech_stack. There is no mixing of conventions or vague verbs.
Three tools is a reasonable size for a focused lead-generation server. However, lookup_tech_stack feels somewhat redundant with research_company, so the count is appropriate but not perfectly scoped.
The core lead-generation workflow is covered: research a company, find contacts, and identify technologies. Obvious gaps remain, such as email verification, lead list management, or exporting results, and the tech-stack lookup is already partially included in research_company.