# B2B Lead Enrichment (remote · lead-enrichment-mcp.agent-infra.workers.dev)

Remote MCP server to enrich company profiles with structured B2B data and confidence scores.

- Trust score: 70/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `lead-enrichment-mcp.agent-infra.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/diego-costa-tech-lead-enrichment-mcp/lead-enrichment-mcp.md), [page](https://verifymcp.io/servers/diego-costa-tech-lead-enrichment-mcp/lead-enrichment-mcp)

## Channel facts

- Endpoint: `https://lead-enrichment-mcp.agent-infra.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 126 tokens (~126/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http diego-costa-tech-lead-enrichment-mcp https://lead-enrichment-mcp.agent-infra.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.diego-costa-tech-lead-enrichment-mcp]
url = "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "diego-costa-tech-lead-enrichment-mcp": {
      "type": "remote",
      "url": "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add diego-costa-tech-lead-enrichment-mcp --url https://lead-enrichment-mcp.agent-infra.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  diego-costa-tech-lead-enrichment-mcp:
    url: "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "diego-costa-tech-lead-enrichment-mcp": {
      "type": "http",
      "url": "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (1)

### `enrich_lead` (~126 tokens)

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.

Input parameters:

- `attributes` (array): Which data attributes to include. Allowed values: firmographic, technographic, intent, contacts.
- `domain` (string, required): The company domain to enrich (e.g., "stripe.com").
- `requiredFields` (array): Specific fields that must be present in the response.

Output parameters:

- `companyName` (string): Official legal name of the enriched company.
- `confidenceScore` (number): Confidence score from 0 to 1.
- `contacts` (array): Key contacts identified at the company.
- `employeeCount` (string): Estimated employee count range (e.g., "5000+").
- `enrichedAt` (string): ISO 8601 timestamp when this enrichment was performed.
- `industry` (string): Primary industry classification.
- `insights` (array): Actionable semantic insights derived from the data.
- `intentSignals` (array): Signals showing buying intent or strategic initiatives.
- `revenue` (string): Estimated annual revenue range (e.g., "$1B+").
- `technologies` (array): Technology stack associated with the company.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/diego-costa-tech-lead-enrichment-mcp/lead-enrichment-mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 64

## Links

- Remote endpoint: https://lead-enrichment-mcp.agent-infra.workers.dev/mcp
- Repository: https://github.com/Diego-Costa-Tech/lead-enrichment-mcp
- Website: https://lead-enrichment-mcp.agent-infra.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/diego-costa-tech-lead-enrichment-mcp/lead-enrichment-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/diego-costa-tech-lead-enrichment-mcp/lead-enrichment-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/diego-costa-tech-lead-enrichment-mcp/lead-enrichment-mcp