Remote MCP · Endpoint

B2B Lead Enrichment MCP server

No. B2B Lead Enrichment answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lead-enrichment-mcp.agent-infra.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Diego-Costa-Tech/lead-enrichment-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
470 ms
Tools exposed
1 tool
Uptime, last 30 days
72.2% from 18 checks
Described by its publisher as
Remote MCP server to enrich company profiles with structured B2B data and confidence scores.
Website
https://lead-enrichment-mcp.agent-infra.workers.dev/
Repository
https://github.com/Diego-Costa-Tech/lead-enrichment-mcp
Listing
From the official MCP registry (active).
Recent checks of B2B Lead Enrichment
CheckedResultHandshake
1 hour agoHandshake completed470 ms
1 day agoFailed - the server returned an HTTP error—
2 days agoHandshake completed537 ms
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoHandshake completed463 ms
6 days agoFailed - the server returned an HTTP error—
9 days agoHandshake completed315 ms
11 days agoHandshake completed483 ms
14 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed548 ms
18 days agoHandshake completed454 ms
20 days agoHandshake completed735 ms
22 days agoHandshake completed516 ms
24 days agoHandshake completed427 ms
26 days agoHandshake completed495 ms
27 days agoHandshake completed434 ms
29 days agoHandshake completed439 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with B2B Lead Enrichment and makes no claim about it beyond what these checks measured.