B2B Lead Enrichment
REMOTE · LEAD-ENRICHMENT-MCP.AGENT-INFRA.WORKERS.DEV · SCANNED AUG 3
Remote MCP server to enrich company profiles with structured B2B data and confidence scores.
Available components
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. How we score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 126 tokens (~126/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · lead-enrichment-mcp.agent-infra.workers.dev
claude mcp add --transport http diego-costa-tech-lead-enrichment-mcp https://lead-enrichment-mcp.agent-infra.workers.dev/mcp
[mcp_servers.diego-costa-tech-lead-enrichment-mcp] url = "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp"
{
"$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 mcp add diego-costa-tech-lead-enrichment-mcp --url https://lead-enrichment-mcp.agent-infra.workers.dev/mcp --transport streamable-http
mcp_servers:
diego-costa-tech-lead-enrichment-mcp:
url: "https://lead-enrichment-mcp.agent-infra.workers.dev/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://lead-enrichment-mcp.agent-infra.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agent-infra.workers.dev | CN=WE1,O=Google Trust Services,C=US | 20 Jun 2026 | 18 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 35d6374c91a99a813f9c8645f726f25 |
| SANs: agent-infra.workers.dev, *.agent-infra.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of lead-enrichment-mcp.agent-infra.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lead-enrichment-mcp.agent-infra.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://lead-enrichment-mcp.agent-infra.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
enrich_lead ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | array | — | Which data attributes to include. Allowed values: firmographic, technographic, intent, contacts. |
| domain | string | yes | The company domain to enrich (e.g., "stripe.com"). |
| requiredFields | array | — | Specific fields that must be present in the response. |
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | Official legal name of the enriched company. |
| confidenceScore | number | yes | Confidence score from 0 to 1. |
| contacts | array | — | Key contacts identified at the company. |
| employeeCount | string | yes | Estimated employee count range (e.g., "5000+"). |
| enrichedAt | string | yes | ISO 8601 timestamp when this enrichment was performed. |
| industry | string | yes | Primary industry classification. |
| insights | array | yes | Actionable semantic insights derived from the data. |
| intentSignals | array | yes | Signals showing buying intent or strategic initiatives. |
| revenue | string | yes | Estimated annual revenue range (e.g., "$1B+"). |
| technologies | array | yes | Technology stack associated with the company. |
No examples provided.