HeyLead MCP

70/100

Capped at 70: no passing tool call yet; the tests add up to 95. Why scores are capped

Last tested 2026-11-18 UTC (Fresh: tested within 30 days) Connects · tools listedNo tool call tested yet Connects without a key; tool calls need one

Advisories: not yet checked

Security review: not tested

Test points add up to 95; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (95/100)

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs10/15
  • License10/10

Tested pypi heylead 0.10.523 (MIT; repo D4umak/linkedin-outreach-mcp). Installed pinned with scripts off (uv venv, Python 3.13) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 22 tools (22 annotated by the server: 9 read-only, 13 destructive). Real calls: 0 of 3 real function calls passed. Calls need a HeyLead profile and connected LinkedIn account (setup_profile). Core tools not tested: 70 cap.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. Calls need a HeyLead profile and connected LinkedIn account (setup_profile). Evidence: local test run, Nov 18, 2026 UTC.

Transport (tested 2026-11-18 UTC): stdio

Token cost (estimate): approx. 8447 tokens, cl100k estimate (22 tools, measured 2026-11-18 UTC, version 0.10.523). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 4 read, 8 write (state-changing), 10 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown

Auth: API key. Rate limit: unknown. Pricing unit: unknown.

  • account — unclassified
  • accounts — unclassified
  • analytics — unclassified
  • answer_inbox — unclassified
  • book_meeting — write (state-changing)
  • campaign — write (state-changing)
  • campaign_status — read
  • check_replies — unclassified
  • contacts — unclassified
  • create_campaign — write (state-changing)
  • edit_campaign — write (state-changing)
  • generate_icp — write (state-changing)
  • inbox — unclassified
  • prospect — unclassified
  • prospect_view — read
  • scheduler — unclassified
  • scheduler_status — read
  • send_message — write (state-changing)
  • setup_profile — write (state-changing)
  • show_status — read
  • suggest_next_action — unclassified
  • update_contact — write (state-changing)

listing-flags calls_need_key or auth_kind

Score 70/100 · Tools 22 · Token cost approx. 8,447 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 0.10.523 · Package heylead · Repo D4umak/linkedin-outreach-mcp

Summary: HeyLead MCP completed an MCP handshake without credentials and exposed 22 tools.

Evidence summary

Handshake
pass
Tools listed
22
Context cost
approx. 8447 tokens, cl100k estimate (22 tools, measured 2026-11-18 UTC, version 0.10.523; an estimate) ranking · add up your servers' context cost
API key
Connects without a key; tool calls need one
Tested
2026-11-18 UTC

Test results

TestResultPointsEvidence
installpass20uv pip install heylead (Python venv, Linux) succeeded in 1s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 22 tools listed in 15.5s.
maintenancepass25Repo pushed 0 days before test; 13 GitHub stars.
docspartial10README over 3,000 chars; install instructions present. Check of the package's own README (PyPI long_description (package README)).
licensepass10MIT (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 8447 tokens, cl100k estimate for 22 tools · about 103% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-18 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 22 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

2fe7462313ad: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "heylead",
  "version": "0.10.523",
  "registry": "pypi",
  "status": "working",
  "tested": "2026-11-18",
  "tools_count": 22,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`uv pip install heylead` (Python venv, Linux) succeeded in 1s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 22 tools listed in 15.5s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 13 GitHub stars."
    ],
    "docs": [
      "partial",
      10,
      "README over 3,000 chars; install instructions present. Check of the package's own README (PyPI long_description (package README))."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  },
  "testedAt": "2026-11-18T04:18:30.851Z"
}

Install

uvx heylead

Pin the version we tested

uvx heylead==0.10.523

pip install heylead==0.10.523

tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "heylead-mcp": {
      "command": "uvx",
      "args": [
        "heylead==0.10.523"
      ]
    }
  }
}

Tools listed

setup_profile, generate_icp, create_campaign, book_meeting, check_replies, show_status, send_message, suggest_next_action, edit_campaign, analytics, accounts, campaign_status, prospect_view, scheduler_status, update_contact, answer_inbox, account, campaign, prospect, scheduler, contacts, inbox

Quick config

{
  "mcpServers": {
    "heylead-mcp": {
      "command": "uvx",
      "args": [
        "heylead"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run uv pip install heylead (Python venv). This is the exact command we ran on 2026-11-18 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (22 in our test).
{
  "mcpServers": {
    "heylead-mcp": {
      "command": "uvx",
      "args": [
        "heylead"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

FAQ

Is HeyLead MCP deprecated?

No. HeyLead MCP was not deprecated or archived when we last tested it on 2026-11-18 UTC.

What replaces HeyLead MCP?

Nothing; HeyLead MCP is not deprecated as of 2026-11-18 UTC.

Does HeyLead MCP need an API key?

It connects and lists 22 tools without a key, but its tool calls need one.

Embed the badge

TestedMCP: 70/100, tested 2026-11-18 UTC

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue