Koskamo

Lead Enrichment MCP

A remote MCP server that provides AI agents with structured B2B company intelligence, including firmographic, technographic, and intent data, along with confidence scores. It supports integration with agents like Claude, Cursor, and VS Code via a single tool call to enrich leads.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Lead Enrichment MCP logo, by Diego-Costa-TechCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by Diego-Costa-Tech
You need:Instant API key after checkoutAuthorization: Bearer your-api-key
MCP endpoint (Streamable HTTP)
https://lead-enrichment-mcp.agent-infra.workers.dev/mcp
Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (1)

1 of 1 have a description · 1 of 1 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Enrich B2B company profiles with firmographic data
  • Retrieve technographic information about target companies
  • Analyze intent signals for lead qualification
  • Generate structured JSON output for AI agents

Source and maintenance

Community listingRegistry 1.0.0
Maintenance checked

Protocol and capabilities

Server
lead-enrichment-mcp 1.0.0
MCP protocol negotiated in check
2025-03-26
Tools
1 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Tools

1 advertised

enrich_lead
Advertised by the server during the last successful anonymous check.
Advertised read-only

Enrich a B2B company profile with structured firmographic, technographic, intent, and contact data. This tool should be called when an AI agent needs to gather detailed information about a company before crafting a personalized outreach, generating a lead score, or making a sales recommendation.

enrich_lead input schema
{
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "title": "Domain",
      "description": "The company domain to enrich (e.g., \"stripe.com\")."
    },
    "attributes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "title": "Attributes",
      "description": "Which data attributes to include. Allowed values: firmographic, technographic, intent, contacts."
    },
    "requiredFields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "title": "Required Fields",
      "description": "Specific fields that must be present in the response."
    }
  }
}
enrich_lead output schema
{
  "type": "object",
  "required": [
    "companyName",
    "industry",
    "employeeCount",
    "revenue",
    "technologies",
    "intentSignals",
    "confidenceScore",
    "enrichedAt",
    "insights"
  ],
  "properties": {
    "revenue": {
      "type": "string",
      "description": "Estimated annual revenue range (e.g., \"$1B+\")."
    },
    "contacts": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "title",
          "department"
        ],
        "properties": {
          "name": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "linkedin": {
            "type": "string"
          },
          "department": {
            "type": "string"
          }
        }
      },
      "description": "Key contacts identified at the company."
    },
    "industry": {
      "type": "string",
      "description": "Primary industry classification."
    },
    "insights": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Actionable semantic insights derived from the data."
    },
    "enrichedAt": {
      "type": "string",
      "format": "date-time",
      "description": "ISO 8601 timestamp when this enrichment was performed."
    },
    "companyName": {
      "type": "string",
      "description": "Official legal name of the enriched company."
    },
    "technologies": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Technology stack associated with the company."
    },
    "employeeCount": {
      "type": "string",
      "description": "Estimated employee count range (e.g., \"5000+\")."
    },
    "intentSignals": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Signals showing buying intent or strategic initiatives."
    },
    "confidenceScore": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Confidence score from 0 to 1."
    }
  }
}
enrich_lead annotations
{
  "title": "Enrich Company Profile",
  "readOnlyHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 2 answered).

  1. 2026-11-07: 0 of 1 checks answered
  2. 2026-11-09: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1294 ms
95th percentile latency
1294 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1294 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http lead-enrichment-mcp https://lead-enrichment-mcp.agent-infra.workers.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add lead-enrichment-mcp --url https://lead-enrichment-mcp.agent-infra.workers.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable lead-enrichment-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "lead-enrichment-mcp": {
      "url": "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "lead-enrichment-mcp": {
      "type": "streamableHttp",
      "url": "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start lead-enrichment-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "lead-enrichment-mcp": {
      "type": "http",
      "url": "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http lead-enrichment-mcp https://lead-enrichment-mcp.agent-infra.workers.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://lead-enrichment-mcp.agent-infra.workers.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "lead-enrichment-mcp": {
      "serverUrl": "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Lead Enrichment MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.