Marketing

getcleed.com

Manages sales prospects and buying-signal-based outreach by listing and retrieving prospects, signal definitions, ICP targeting, and pipeline statistics.

1 endpoint15 known toolsFirst detected September 25, 2026Last detected September 25, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: getcleed
Version: 1.0.0

Capabilities

tools

Server instructions

getcleed finds B2B prospects showing buying signals on LinkedIn and drafts the outreach. Start with get_pipeline_stats for the lay of the land, list_signals to see what this account treats as a buying signal, and get_icp for who it targets. list_prospects and get_prospect read the pipeline; every signal carries the verbatim quote from the post it came from, so quote that rather than paraphrasing. To grow the pipeline: find_leads_from_signals searches recent LinkedIn posts on the account's own signal topics and returns ICP-matching people (nothing is saved until import_sourced_leads), add_leads_from_urls saves specific profiles, and analyze_prospects detects signals on prospects that have none. send_email and send_linkedin_message reach real people immediately and cannot be undone. Show the user the draft and get their agreement before calling them.

Known tools 15

list_prospects

Search the saved prospects in the account.

Inferred read-only

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.

Potential side effects

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.

Potential side effects

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.

Inferred read-only

get_icp

The active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions.

Inferred read-only

add_leads_from_urls

Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language).

Inferred read-only

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.

Inferred read-only

import_sourced_leads

Save candidates returned by find_leads_from_signals.

Inferred read-only

analyze_prospects

Run the signal pipeline on prospects: enrich anyone missing company data, read their recent LinkedIn activity, and detect buying signals.

Inferred read-only

draft_email

Write a personalised email for a prospect, built from their detected signals, in their language.

Potential side effects

draft_linkedin_message

Write a short LinkedIn connection note for a prospect from their detected signals, in their language.

Potential side effects

send_email

Send an email to a prospect from the connected mailbox.

Potential side effects

send_linkedin_message

Send a LinkedIn connection request with a note to a prospect from the connected LinkedIn account.

Potential side effects

mark_email_sent

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

Inferred read-only

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").

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.getcleed]
url = "https://www.getcleed.com/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: getcleed
Remote MCP URL: https://www.getcleed.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "getcleed": {
      "url": "https://www.getcleed.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "getcleed",
  "transport": "streamable-http",
  "url": "https://www.getcleed.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.