mcpbeat

HeyLead — Autonomous LinkedIn SDR MCP Server

io.github.D4umak/heylead
not responding

HeyLead — Autonomous LinkedIn SDR is listed as active in the registry but did not answer our last check. 2 114 installs a week from pypi.

Autonomous LinkedIn SDR — voice-matched outreach, ICP generation, and campaign management.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 777 · avg 276 · +58% w/w
a month agotoday
Uptime history 41 hours of history · worst hour 0%
41 hours agonow
0.0%
Uptime 24h
0 of 92 checks
—
Tools
hidden behind auth
235 ms
Response time
average over 24h
2 114
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add heylead --transport http https://heylead-api-141730336364.us-central1.run.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "heylead": {
      "url": "https://heylead-api-141730336364.us-central1.run.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.heylead]
url = "https://heylead-api-141730336364.us-central1.run.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "heylead": {
      "url": "https://heylead-api-141730336364.us-central1.run.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "heylead": {
      "url": "https://heylead-api-141730336364.us-central1.run.app/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://heylead-api-141730336364.us-central1.run.app/mcp streamable-http answering 235 ms 0 min ago

HeyLead — Autonomous LinkedIn SDR — questions

Answers built from our own checks of this server.

Is HeyLead — Autonomous LinkedIn SDR working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 235 ms. The bar chart above shows every period we have measured.
Is HeyLead — Autonomous LinkedIn SDR still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists HeyLead — Autonomous LinkedIn SDR as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect HeyLead — Autonomous LinkedIn SDR?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does HeyLead — Autonomous LinkedIn SDR need an API key?
No. HeyLead — Autonomous LinkedIn SDR completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How many people use HeyLead — Autonomous LinkedIn SDR?
The pypi package heylead was installed 2 114 times in the last week. Week over week that is +58%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.