# com.getcleed/linkedin-buying-signals (remote · www.getcleed.com)

Find B2B prospects showing buying signals on LinkedIn and draft the outreach.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `www.getcleed.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-getcleed-linkedin-buying-signals/api-mcp.md), [page](https://verifymcp.io/servers/com-getcleed-linkedin-buying-signals/api-mcp)

## Channel facts

- Endpoint: `https://www.getcleed.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-02.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1533 tokens (~102/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 48% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.getcleed/linkedin-buying-signals MCP server?

com.getcleed/linkedin-buying-signals is a hosted endpoint at https://www.getcleed.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-getcleed-linkedin-buying-signals 'https://www.getcleed.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-getcleed-linkedin-buying-signals": {
      "url": "https://www.getcleed.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-getcleed-linkedin-buying-signals": {
      "type": "http",
      "url": "https://www.getcleed.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-getcleed-linkedin-buying-signals]
url = "https://www.getcleed.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getcleed-linkedin-buying-signals": {
      "type": "remote",
      "url": "https://www.getcleed.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-getcleed-linkedin-buying-signals --url 'https://www.getcleed.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-getcleed-linkedin-buying-signals:
    url: "https://www.getcleed.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-getcleed-linkedin-buying-signals": {
      "Transport": "http",
      "Url": "https://www.getcleed.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-getcleed-linkedin-buying-signals -t streamable-http -u 'https://www.getcleed.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-getcleed-linkedin-buying-signals": {
      "type": "http",
      "url": "https://www.getcleed.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-29 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 78, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-26 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-25 (score 77)

First indexed and scored.

## MCP tools (15)

### `list_prospects` (~208 tokens)

List prospects

Search the saved prospects in the account. Filter by company, industry, job title, country, signal type, minimum number of signals, whether an email address is known, enrichment state, or whether they have been contacted. Ordered by signal count, then most recently saved.

Input parameters:

- `company` (string)
- `country` (string)
- `enrichmentStatus` (string)
- `hasEmail` (boolean)
- `industry` (string)
- `limit` (integer): How many to return (max 50)
- `minSignals` (integer): Only prospects with at least this many signals
- `notContacted` (boolean): Only prospects with no email sent yet
- `offset` (integer)
- `search` (string): Free text matched against first name, last name, company and title
- `signalType` (string): Only prospects carrying a signal of this type (see list_signals)
- `title` (string): Job title contains this text

### `get_prospect` (~90 tokens)

Get one prospect

Everything known about one prospect: role, company, location, language, every detected signal with the verbatim quote from its source and the LinkedIn URL it came from, any existing email or LinkedIn draft, and outreach state.

Input parameters:

- `linkedinUrl` (string): Their LinkedIn profile URL, if the id is unknown
- `prospectId` (string): The prospect id from list_prospects

### `get_pipeline_stats` (~60 tokens)

Pipeline stats

How the pipeline stands: how many prospects, how many carry signals, enrichment state, how many have an email address, how many were contacted, what was added in the last 7 days, the most common signal types, and the remaining plan quota.

### `list_signals` (~65 tokens)

List signal definitions

The buying signals this account looks for: the predefined ones and the custom ones, each with the definition used to detect it and whether it is enabled. Use the returned type values with list_prospects and find_leads_from_signals.

Input parameters:

- `enabledOnly` (boolean)

### `get_icp` (~38 tokens)

Get the ideal customer profile

The active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions. This is what sourcing and scoring filter against.

### `add_leads_from_urls` (~79 tokens)

Add leads from LinkedIn URLs

Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language). Skips anyone already saved. Counts against the import quota.

Input parameters:

- `linkedinUrls` (array, required): LinkedIn profile URLs
- `listId` (string): Optional list to add them to (see get_icp for list ids)

### `find_leads_from_signals` (~127 tokens)

Find new leads from signal topics

Search recent LinkedIn posts on the topics of this account's own signal definitions, keep only posts a check can prove are on topic, and return the people who wrote, commented on or reacted to them, filtered against the ICP (role, industry, country) and ranked. Nothing is saved: pass the returned candidates to import_sourced_leads. Spends a little of the monthly sourcing budget.

Input parameters:

- `postsPerSignal` (integer)
- `signalType` (string): Which signal to source for; omit to use the first enabled one (see list_signals)

### `import_sourced_leads` (~92 tokens)

Import sourced leads

Save candidates returned by find_leads_from_signals. They arrive already enriched and with the signal attached, including the verbatim quote from the post that surfaced them. Counts against the import quota.

Input parameters:

- `listId` (string)
- `signalType` (string, required): The signalType returned by find_leads_from_signals
- `tokens` (array, required): The token values of the candidates to import

### `analyze_prospects` (~95 tokens)

Analyze prospects

Run the signal pipeline on prospects: enrich anyone missing company data, read their recent LinkedIn activity, and detect buying signals. Every signal kept must quote its source verbatim. Counts against the monthly analysis quota. Slow: expect up to a few minutes.

Input parameters:

- `limit` (integer): Cap when prospectIds is omitted
- `prospectIds` (array): Which prospects to analyze; omit to take those with no signals yet

### `draft_email` (~87 tokens)

Draft an email

Write a personalised email for a prospect, built from their detected signals, in their language. Saves the draft on the prospect and returns it. Does not send.

Input parameters:

- `language` (string)
- `linkedinUrl` (string)
- `prospectId` (string)
- `regenerate` (boolean): Ignore any cached draft
- `signalIndex` (integer): Which signal to lead with

### `draft_linkedin_message` (~70 tokens)

Draft a LinkedIn message

Write a short LinkedIn connection note for a prospect from their detected signals, in their language. Saves the draft and returns it. Does not send.

Input parameters:

- `language` (string)
- `linkedinUrl` (string)
- `prospectId` (string)
- `regenerate` (boolean)

### `send_email` (~104 tokens)

Send an email

Send an email to a prospect from the connected mailbox. This reaches a real person immediately and cannot be undone. Pass the subject and body you want sent, or omit them to send the saved draft. Requires a mailbox connected in getcleed under Integrations.

Input parameters:

- `body` (string): Omit to use the saved draft
- `linkedinUrl` (string)
- `prospectId` (string)
- `subject` (string): Omit to use the saved draft

### `send_linkedin_message` (~106 tokens)

Send a LinkedIn connection request

Send a LinkedIn connection request with a note to a prospect from the connected LinkedIn account. This reaches a real person immediately and cannot be undone. Pass the note you want sent, or omit it to use the saved draft. Requires LinkedIn connected in getcleed under Integrations.

Input parameters:

- `linkedinUrl` (string)
- `message` (string): The note, max 300 characters. Omit to use the saved draft
- `prospectId` (string)

### `mark_email_sent` (~44 tokens)

Mark as contacted

Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.

Input parameters:

- `linkedinUrl` (string)
- `prospectId` (string)

### `create_custom_signal` (~85 tokens)

Create a custom signal

Teach the account a new buying signal to look for, described in plain language (for example "people complaining their onboarding takes too long"). Future analyses and sourcing will use it.

Input parameters:

- `detects` (string, required): What to look for, in plain language
- `exampleDetail` (string)
- `exampleTitle` (string)
- `name` (string, required): Short display name

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-getcleed-linkedin-buying-signals/api-mcp#diagnostics

## Score history

- 2026-10-02: 80
- 2026-10-01: 80
- 2026-09-30: 79
- 2026-09-29: 79
- 2026-09-28: 78
- 2026-09-27: 78
- 2026-09-26: 77
- 2026-09-25: 77

## Common questions

### What is the com.getcleed/linkedin-buying-signals MCP server?

com.getcleed/linkedin-buying-signals is an MCP server listed in the public MCP registry as com.getcleed/linkedin-buying-signals. Find B2B prospects showing buying signals on LinkedIn and draft the outreach. This page covers its hosted endpoint (https://www.getcleed.com/api/mcp).

### Is the com.getcleed/linkedin-buying-signals MCP server safe to use?

com.getcleed/linkedin-buying-signals scores 80 out of 100 on VerifyMCP. 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 com.getcleed/linkedin-buying-signals MCP server expose?

com.getcleed/linkedin-buying-signals exposes 15 tools: list_prospects, get_prospect, get_pipeline_stats, list_signals, get_icp, and 10 more. Their descriptions and schemas cost roughly 1,350 tokens of context every time the server is loaded.

### Does the com.getcleed/linkedin-buying-signals MCP server require authentication?

Yes. com.getcleed/linkedin-buying-signals asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the com.getcleed/linkedin-buying-signals MCP server still maintained?

com.getcleed/linkedin-buying-signals is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.getcleed.com/api/mcp
- Repository: https://github.com/nossa-y/hp-auto-deploy
- Website: https://www.getcleed.com/claude
- Changelog RSS feed: https://verifymcp.io/servers/com-getcleed-linkedin-buying-signals/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getcleed-linkedin-buying-signals/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-getcleed-linkedin-buying-signals/api-mcp