Linkedin Buying Signals MCP Server

by getcleed Your server? Claim it

not responding

Linkedin Buying Signals is listed as active in the registry but did not answer our last check. It exposes 16 tools.

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

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

Uptime history 44 days of history · worst day 0%

44 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

79 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.

25 Oct a tool appeared get_sample_pipeline

25 Oct a tool description was rewritten draft_linkedin_message

Linkedin Buying Signals does not always answer

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://www.getcleed.com/api/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

draft

draft_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.

draft_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. Drafts follow the house rules (one fact about them, one question, no pitch, under 200 characters) and so must any note passed to send_linkedin_message.

leads

add_leads_from_urls

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

find_leads_from_signals

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.

send

send_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.

send_linkedin_message

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.

analyze

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.

custom

create_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.

icp

get_icp

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

import

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.

mark

mark_email_sent

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

pipeline

get_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.

prospect

get_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.

prospects

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.

sample

get_sample_pipeline

A fictional pipeline in exactly the shapes the real tools return: an ICP, the signal definitions, pipeline stats and six prospects with their signals, verbatim quotes and drafts. Works without any credential, so an agent can show what Getcleed produces before an account exists. Nothing in it is a real person.

signals

list_signals

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.

Endpoints

URL	Transport	State	Latency	Checked
https://www.getcleed.com/api/mcp	streamable-http	answering	79 ms	1 min ago

Alternatives to Linkedin Buying Signals

same job, measured the same way

Kairon

by heykairon

Build prospecting lists from buying signals, enrich them, and run LinkedIn outreach.

answering

Hilead

by hilead

Signal-based B2B prospecting: find leads with buying intent, run email and LinkedIn outreach.

answering

Omentir

by vanshyadav1408

Find LinkedIn prospects, draft outreach, and run human-paced campaigns from your AI agent.

answering

Relinta

by relinta

LinkedIn prospecting, daily post signals, outreach campaigns and inbox management.

answering

Oneprofile

by getoneprofile

Find prospects, research them, and run email and LinkedIn outreach in your Oneprofile workspace.

answering

Funkel AI

by funkel

Run LinkedIn and email outreach: find leads, manage campaigns, and reply to prospects.

51 tools answering

Signado MCP

by signado

LinkedIn warm-lead discovery: list leads, find emails, and draft outreach from your AI tools.

answering

Fintalio LinkedIn MCP

by fintalio

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

answering

Linkedin Buying Signals — questions

Answers built from our own checks of this server.

What can Linkedin Buying Signals do?

It exposes 16 tools, read directly from the server on our last check. Among them: add_leads_from_urls, analyze_prospects, create_custom_signal, draft_email, draft_linkedin_message, find_leads_from_signals and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Linkedin Buying Signals mostly used for?

Its tools cluster around send, leads and draft. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Linkedin Buying Signals 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 79 ms. The bar chart above shows every period we have measured.

Is Linkedin Buying Signals 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 Linkedin Buying Signals 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 Linkedin Buying Signals?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Linkedin Buying Signals need an API key?

No. Linkedin Buying Signals completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.