mcpbeat Sign in

HeyLead — Autonomous LinkedIn SDR MCP Server

by d4umak Your server? Claim it
answering

HeyLead — Autonomous LinkedIn SDR is answering right now. Last checked 3 min ago. 7 717 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 8 461 · avg 2 000 · -64% w/w
a month agotoday
Uptime history 51 days of history · worst day 0%
51 days agonow
47.8%
Uptime 24h
87 of 182 checks
—
Tools
hidden behind auth
470 ms
Response time
average over 24h
7 717
Installs / week
npm and PyPI

HeyLead — Autonomous LinkedIn SDR does not always answer

Over the last week it answered 30.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

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

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Endpoints

URLTransportStateLatencyChecked
https://heylead-api-141730336364.us-central1.run.app/mcp streamable-http answering 191 ms 4 min ago
https://heylead.dev/mcp streamable-http sign-in 347 ms 3 min ago

Alternatives to HeyLead — Autonomous LinkedIn SDR

same job, measured the same way
LinkedIn Campaign Manager
by zleventer

MCP server for LinkedIn Ads — 19 read-only tools for campaigns, performance, and Lead Gen Forms.

16 installs/wk local only
Linkedin Ads
by mharnett

MCP server for LinkedIn Campaign Manager — campaigns, creatives, and analytics

33 installs/wk local only
Bavlio
by bavlio

LinkedIn + cold email outreach: find leads, launch personalized campaigns, manage replies.

answering
Campaignstack
by campaignstack

Run B2B outreach from your AI agent: 250+ tools for campaigns, leads, LinkedIn and email workflows.

answering
LinkedNav
by linglistack

Run LinkedIn outreach from your AI chat: find leads, launch campaigns, send, and reply.

answering
Highstory MCP
by 7figures007

High Story MCP Server - Automate AI content campaigns and social media management.

51 installs/wk local only
Pro Reach LinkedIn Outreach
by proreach

Plan and run LinkedIn outreach: templates, leads, confirmation-gated launch, metrics, replies.

answering
Fintalio LinkedIn MCP
by fintalio

LinkedIn outreach MCP server — 19 tools for AI agents to prospect, sequence, and manage contacts.

answering

HeyLead — Autonomous LinkedIn SDR — questions

Answers built from our own checks of this server.

Why is there no tool list for HeyLead — Autonomous LinkedIn SDR?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 47.8% of checks in the last 24 hours got a reply.
Is HeyLead — Autonomous LinkedIn SDR working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 87 of 182 checks got a reply (47.8%), average response time 470 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.
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. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to HeyLead — Autonomous LinkedIn SDR?
No API key is involved. HeyLead — Autonomous LinkedIn SDR answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is HeyLead — Autonomous LinkedIn SDR?
It answers our handshake in 470 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use HeyLead — Autonomous LinkedIn SDR?
The pypi package heylead was installed 7 717 times in the last week. Week over week that is -64%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.