com.zalize.leads/leadsleuth

com.zalize.leads/leadsleuth

com.zalize.leads/leadsleuth did not answer the probe on 2026-10-03. Result: needs auth (HTTP 401).

B2B leads: scored buying signals from HN/Bluesky/GitHub with AI dossiers and outreach drafts.

needs auth probed 2026-10-03 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"unauthorized","message":"Missing Bearer API key or OAuth access token."}}

Endpoint

https://leads.zalize.com/api/mcp (streamable-http)

Host

leads.zalize.com

Repository

https://github.com/wookat/leadsleuth

Website

https://leads.zalize.com/docs/mcp

Registry

active, updated 2026-08-11 · registry entry

Reachable

2 of the last 2 probes

History

We add a row when the result changes. A server with no change keeps its last row.

Badge

[![mcp-pulse](https://mcp-pulse.ulehla.dev/badge/com.zalize.leads/leadsleuth.svg)](https://mcp-pulse.ulehla.dev/s/com.zalize.leads/leadsleuth)