Getcleed MCP server

Which servers in the official MCP registry are Getcleed's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-10

← Back to Getcleed

Whose server it is

Registry namecom.getcleed/linkedin-buying-signalsverified in the MCP registry

The registry name sits under getcleed.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-10

Stateanswerschecked 2026-10-10
Tools15
Server calls itselfgetcleed
Server version1.0.0
Protocol version2025-06-18

On 2026-10-10 the server answered initialize and tools/list without a sign-in. First answer in 1357 ms.

Tools it offers15 tools · read 2026-10-10

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…
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.
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.
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.
get_icp
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
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…
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.
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…
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.
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…
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…
mark_email_sent
Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.
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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.