LeadFuze-MCP-Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEADFUZE_API_KEY | Yes | Your LeadFuze API key (starts with lfz_). Find it on the API Keys page at https://console.leadfuze.com/ |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| enrich_by_emailA | Look up detailed person and company information using an email address. Returns verified business data including job title, company details, phone numbers, and social profiles. |
| enrich_by_linkedinA | Look up detailed person and company information using a LinkedIn profile URL. Returns verified business data including email, job title, company details, and phone numbers. |
| validate_emailA | Validate an email address to check if it's deliverable, has valid format, and assess its risk level. Returns detailed validation results including deliverability, catch-all status, and mail server information. |
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
Each tool has a clearly distinct purpose: enrich_by_email and enrich_by_linkedin both enrich contact data but use different input types (email vs. LinkedIn URL), while validate_email performs a separate validation function. There is no ambiguity or overlap in their core operations.
All tool names follow a consistent verb_noun pattern with snake_case (enrich_by_email, enrich_by_linkedin, validate_email). The naming is predictable and readable across the set.
Three tools is reasonable for a lead enrichment and validation server, though it feels slightly minimal. Each tool earns its place, but the scope could potentially support a few more related operations without being overburdened.
The tools cover key enrichment and validation workflows for lead data, with no obvious dead ends. Minor gaps might include bulk operations or additional data sources, but agents can effectively work with the provided surface for common use cases.