com.getcleed/linkedin-buying-signals
REMOTE · WWW.GETCLEED.COM · SCANNED OCT 2
Find B2B prospects showing buying signals on LinkedIn and draft the outreach.
Available components
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1533 tokens (~102/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · www.getcleed.com
claude mcp add --transport http com-getcleed-linkedin-buying-signals 'https://www.getcleed.com/api/mcp'
{
"mcpServers": {
"com-getcleed-linkedin-buying-signals": {
"url": "https://www.getcleed.com/api/mcp"
}
}
} {
"servers": {
"com-getcleed-linkedin-buying-signals": {
"type": "http",
"url": "https://www.getcleed.com/api/mcp"
}
}
} [mcp_servers.com-getcleed-linkedin-buying-signals] url = "https://www.getcleed.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-getcleed-linkedin-buying-signals": {
"type": "remote",
"url": "https://www.getcleed.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-getcleed-linkedin-buying-signals --url 'https://www.getcleed.com/api/mcp' --transport streamable-http
mcp_servers:
com-getcleed-linkedin-buying-signals:
url: "https://www.getcleed.com/api/mcp" {
"McpServers": {
"com-getcleed-linkedin-buying-signals": {
"Transport": "http",
"Url": "https://www.getcleed.com/api/mcp"
}
}
} assistant mcp add com-getcleed-linkedin-buying-signals -t streamable-http -u 'https://www.getcleed.com/api/mcp'
{
"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.
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.
- 1 Oct 26 +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.
- 29 Sept 26 +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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +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.
- 26 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 77
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 2 Oct 2026 · Probed https://www.getcleed.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.getcleed.com | CN=YR2,O=Let's Encrypt,C=US | 7 Aug 2026 | 5 Nov 2026 | RSA 2048 | SHA256-RSA | 595552a9852d0be72b49b1d4c7ea6e464c5 |
| SANs: www.getcleed.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.getcleed.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| getcleed.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://www.getcleed.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://www.getcleed.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://vercel.live https://ddwl4m2hdecbv.cloudfront.net; worker-src 'self' blob: data:; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; connect-src 'self' https: wss:; font-src 'self' data:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-src 'self' https://www.loom.com; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Protected resource metadata
| Document | https://www.getcleed.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.getcleed.com/api/mcp |
| Authorisation server | https://www.getcleed.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.getcleed.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.getcleed.com/api/mcp | HTTPS enforced | 308 | https://www.getcleed.com/api/mcp |
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 →
add_leads_from_urls Add leads from LinkedIn URLs ~79
Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language). Skips anyone already saved. Counts against the import quota.
| Name | Type | Req | Description |
|---|---|---|---|
| linkedinUrls | array | yes | LinkedIn profile URLs |
| listId | string | – | Optional list to add them to (see get_icp for list ids) |
No output schema declared.
No examples provided.
analyze_prospects Analyze prospects ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Cap when prospectIds is omitted |
| prospectIds | array | – | Which prospects to analyze; omit to take those with no signals yet |
No output schema declared.
No examples provided.
create_custom_signal Create a custom signal ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detects | string | yes | What to look for, in plain language |
| exampleDetail | string | – | – |
| exampleTitle | string | – | – |
| name | string | yes | Short display name |
No output schema declared.
No examples provided.
draft_email Draft an email ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| linkedinUrl | string | – | – |
| prospectId | string | – | – |
| regenerate | boolean | – | Ignore any cached draft |
| signalIndex | integer | – | Which signal to lead with |
No output schema declared.
No examples provided.
draft_linkedin_message Draft a LinkedIn message ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| linkedinUrl | string | – | – |
| prospectId | string | – | – |
| regenerate | boolean | – | – |
No output schema declared.
No examples provided.
find_leads_from_signals Find new leads from signal topics ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| postsPerSignal | integer | – | – |
| signalType | string | – | Which signal to source for; omit to use the first enabled one (see list_signals) |
No output schema declared.
No examples provided.
get_icp Get the ideal customer profile ~38
The active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions. This is what sourcing and scoring filter against.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pipeline_stats Pipeline stats ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_prospect Get one prospect ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| linkedinUrl | string | – | Their LinkedIn profile URL, if the id is unknown |
| prospectId | string | – | The prospect id from list_prospects |
No output schema declared.
No examples provided.
import_sourced_leads Import sourced leads ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listId | string | – | – |
| signalType | string | yes | The signalType returned by find_leads_from_signals |
| tokens | array | yes | The token values of the candidates to import |
No output schema declared.
No examples provided.
list_prospects List prospects ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
list_signals List signal definitions ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| enabledOnly | boolean | – | – |
No output schema declared.
No examples provided.
mark_email_sent Mark as contacted ~44
Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.
| Name | Type | Req | Description |
|---|---|---|---|
| linkedinUrl | string | – | – |
| prospectId | string | – | – |
No output schema declared.
No examples provided.
send_email Send an email ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Omit to use the saved draft |
| linkedinUrl | string | – | – |
| prospectId | string | – | – |
| subject | string | – | Omit to use the saved draft |
No output schema declared.
No examples provided.
send_linkedin_message Send a LinkedIn connection request ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| linkedinUrl | string | – | – |
| message | string | – | The note, max 300 characters. Omit to use the saved draft |
| prospectId | string | – | – |
No output schema declared.
No examples provided.
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.