Leadconnector
NPM · @PIPEWORX/MCP-LEADCONNECTOR · 2 COMPONENTS
LeadConnector / GoHighLevel MCP Pack — wraps the GoHighLevel CRM for AI agents.
Available components
Last scanned (18 hours ago)
Scores higher than 72% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-leadconnector). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1258 tokens (~251/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@pipeworx/mcp-leadconnector@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-leadconnector |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-leadconnector/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649645698 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a6eca2efe1d22d927dee5a96f983b728a45575028e2bd42504f411187888cb52ec0639a4b117e8e09e8369bdbab22d5dfd192dea0c6dd264f19fadbf3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
leadconnector_get_contact ~225
Fetch a single CRM contact by its contact ID. Returns full detail: name, email, phone, tags, source, custom fields, and timestamps. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own GoHighLevel/LeadConnector token (BYO — Pipeworx does not supply one). Either a v2 Private Integration Token (`pit-` prefixed; Settings → Private Integrations) — pass `locationId` with it — o… |
| contactId | string | yes | GoHighLevel contact ID |
| locationId | string | – | GoHighLevel sub-account (Location) ID. REQUIRED with a v2 `pit-` token, ignored for a v1 key. It is the id in the dashboard URL: …/location/<locationId>/… |
No output schema declared.
No examples provided.
leadconnector_list_campaigns ~221
List marketing/automation campaigns in the account. Returns a {campaigns:[...]} envelope with campaign IDs, names, and status. Useful for finding a campaign to attribute or enroll contacts. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own GoHighLevel/LeadConnector token (BYO — Pipeworx does not supply one). Either a v2 Private Integration Token (`pit-` prefixed; Settings → Private Integrations) — pass `locationId` with it — o… |
| locationId | string | – | GoHighLevel sub-account (Location) ID. REQUIRED with a v2 `pit-` token, ignored for a v1 key. It is the id in the dashboard URL: …/location/<locationId>/… |
No output schema declared.
No examples provided.
leadconnector_list_contacts ~271
Search or list CRM contacts in a GoHighLevel/LeadConnector account. Free-text query matches name, email, or phone. Returns a {contacts:[...], meta} envelope with contact IDs, names, emails, phones, tags, and custom fields. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own GoHighLevel/LeadConnector token (BYO — Pipeworx does not supply one). Either a v2 Private Integration Token (`pit-` prefixed; Settings → Private Integrations) — pass `locationId` with it — o… |
| limit | number | – | Max contacts to return (default 20, max 100) |
| locationId | string | – | GoHighLevel sub-account (Location) ID. REQUIRED with a v2 `pit-` token, ignored for a v1 key. It is the id in the dashboard URL: …/location/<locationId>/… |
| query | string | – | Free-text search across contact name, email, and phone |
No output schema declared.
No examples provided.
leadconnector_list_opportunities ~263
List opportunities (pipeline deals) for a given pipeline. Requires a pipelineId (get one from leadconnector_list_pipelines). Returns deals with monetary value, stage, status, and the associated contact. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own GoHighLevel/LeadConnector token (BYO — Pipeworx does not supply one). Either a v2 Private Integration Token (`pit-` prefixed; Settings → Private Integrations) — pass `locationId` with it — o… |
| limit | number | – | Max opportunities to return (default 20, max 100) |
| locationId | string | – | GoHighLevel sub-account (Location) ID. REQUIRED with a v2 `pit-` token, ignored for a v1 key. It is the id in the dashboard URL: …/location/<locationId>/… |
| pipelineId | string | yes | Pipeline ID to list opportunities for (from leadconnector_list_pipelines) |
No output schema declared.
No examples provided.
leadconnector_list_pipelines ~225
List all sales pipelines and their stages in the account. Returns a {pipelines:[...]} envelope with pipeline IDs, names, and ordered stages. Use the returned pipeline ID with leadconnector_list_opportunities. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own GoHighLevel/LeadConnector token (BYO — Pipeworx does not supply one). Either a v2 Private Integration Token (`pit-` prefixed; Settings → Private Integrations) — pass `locationId` with it — o… |
| locationId | string | – | GoHighLevel sub-account (Location) ID. REQUIRED with a v2 `pit-` token, ignored for a v1 key. It is the id in the dashboard URL: …/location/<locationId>/… |
No output schema declared.
No examples provided.
How do I install the Leadconnector MCP server?
Leadconnector runs locally as an npm package, launched with npx -y @pipeworx/mcp-leadconnector. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-leadconnector
claude mcp add pipeworx-io-leadconnector -- npx -y @pipeworx/mcp-leadconnector
What is the Leadconnector MCP server?
Leadconnector is an MCP server listed in the public MCP registry as io.github.pipeworx-io/leadconnector. LeadConnector / GoHighLevel MCP Pack, wraps the GoHighLevel CRM for AI agents. This page covers its npm package (@pipeworx/mcp-leadconnector).
Is the Leadconnector MCP server safe to use?
Leadconnector scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Leadconnector MCP server expose?
Leadconnector exposes 5 tools: leadconnector_list_contacts, leadconnector_get_contact, leadconnector_list_pipelines, leadconnector_list_opportunities, leadconnector_list_campaigns. Their descriptions and schemas cost roughly 1,205 tokens of context every time the server is loaded.
Is the Leadconnector MCP server still maintained?
Leadconnector is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Leadconnector MCP server under?
Leadconnector declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.