linkedin-buying-signals MCP server
com.getcleed/linkedin-buying-signalsgetcleed.comstreamable-httpv1.1.0Scanned
Find B2B prospects showing buying signals on LinkedIn and draft the outreach.
16 tools: 2 can delete or cancel things, 8 change things and 6 only read.
- Reads private data · 2
- Reads text others write · 3
- Can send data out · 3
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the linkedin-buying-signals MCP server can do
The linkedin-buying-signals MCP server is published by getcleed.com, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (2 tools: send_email and send_linkedin_message) and create or change data (8 tools: add_leads_from_urls, find_leads_from_signals, import_sourced_leads, analyze_prospects and 4 more). 6 tools only read.
2 tools read private data (get_prospect and get_pipeline_stats); 3 tools bring in text other people can write (get_prospect, get_pipeline_stats and find_leads_from_signals); 3 tools can send data out of your system (send_email, send_linkedin_message and mark_email_sent). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Deletes or cancels 2Claude Code: deny
send_emailSend an email to a prospect from the connected mailbox.Can send data outNo findings
Why it is in this group
- The name "send_email" says "send": a word for sending, and what is sent cannot be taken back.
- The description says "cannot be undone".
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "send_email" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
send_linkedin_messageSend a LinkedIn connection request with a note to a prospect from the connected LinkedIn account.Can send data outNo findings
Why it is in this group
- The name "send_linkedin_message" says "send": a word for sending, and what is sent cannot be taken back.
- The description says "cannot be undone".
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "send_linkedin_message" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
Changes things 8Claude Code: ask
add_leads_from_urlsSave LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language).No findings
Why it is in this group
- The name "add_leads_from_urls" says "add": a word for a change.
Description, as the server wrote it Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language). Skips anyone already saved. Counts against the import quota.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
analyze_prospectsRun the signal pipeline on prospects: enrich anyone missing company data, read their recent LinkedIn activity, and detect buying signals.No findings
Why it is in this group
- The name "analyze_prospects" says "analyze": a word for reading.
- The description's first verb is "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
create_custom_signalTeach the account a new buying signal to look for, described in plain language (for example "people complaining their onboarding takes too long").No findings
Why it is in this group
- The name "create_custom_signal" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
draft_emailWrite a personalised email for a prospect, built from their detected signals, in their language.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
draft_linkedin_messageWrite a short LinkedIn connection note for a prospect from their detected signals, in their language.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
find_leads_from_signalsSearch 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 o…Reads text others write1 finding
Why it is in this group
- The name "find_leads_from_signals" says "find": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe description's first sentence says "search" and "post": it reads posts, which other people can write.
Findings
- Warn
The server marks "find_leads_from_signals" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "find_leads_from_signals" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
import_sourced_leadsSave candidates returned by find_leads_from_signals.No findings
Why it is in this group
- The name "import_sourced_leads" says "import": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
mark_email_sentRecord that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.Can send data outNo findings
Why it is in this group
- The name "mark_email_sent" says "mark": a word for a change.
What it can reach
- outboundThe name "mark_email_sent" says "mark" and "email": it writes something other people read.
Description, as the server wrote it Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Only reads 6Show 6 read-only tools
get_icpThe active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions.No findings
Why it is in this group
- The name "get_icp" says "get": a word for reading.
Description, as the server wrote it The active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions. This is what sourcing and scoring filter against.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_pipeline_statsHow 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, t…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_pipeline_stats" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_prospectEverything 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 existin…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_prospect" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_sample_pipelineA 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.1 finding
Why it is in this group
- The name "get_sample_pipeline" says "get": a word for reading.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...im quotes and drafts. Works without any credential, so an agent can show what Getcleed pro..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
list_prospectsSearch the saved prospects in the account.No findings
Why it is in this group
- The name "list_prospects" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
list_signalsThe 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.No findings
Why it is in this group
- The name "list_signals" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
18 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__linkedin-buying-signals__get_pipeline_stats",
"mcp__linkedin-buying-signals__get_prospect"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:39 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 24
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.getcleed.com/.well-known/oauth-protected-resource
- Authorization servers
- https://www.getcleed.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 24 tools that change things (9 destructive, 15 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.getcleed.com/api/mcp: tools/list returned 38 tools to an anonymous client, including send_email (destructive), send_linkedin_message (destructive), approve_leads (destructive), remove_exclusion (destructive), add_leads_to_sequence (destructive) and 19 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 10 to 24
Findings
Matches of fixed checks, with the text they matched.
The server marks "find_leads_from_signals" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "find_leads_from_signals" says "find": a word for reading.
The description mentions "credential".
What this check looks forMatched text
description: "...im quotes and drafts. Works without any credential, so an agent can show what Getcleed pro..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 24.View diff
- Tools that change things, listed without credentials: 10 to 24
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:get_sample_pipelineOnly reads
- Changed:draft_linkedin_messageChanges thingsdescription
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http linkedin-buying-signals https://www.getcleed.com/api/mcpclaude mcp add --transport http linkedin-buying-signals https://www.getcleed.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__linkedin-buying-signals__get_sample_pipeline",
"mcp__linkedin-buying-signals__list_prospects",
"mcp__linkedin-buying-signals__get_prospect",
"mcp__linkedin-buying-signals__get_pipeline_stats",
"mcp__linkedin-buying-signals__list_signals",
"mcp__linkedin-buying-signals__get_icp"
],
"ask": [
"mcp__linkedin-buying-signals__add_leads_from_urls",
"mcp__linkedin-buying-signals__find_leads_from_signals",
"mcp__linkedin-buying-signals__import_sourced_leads",
"mcp__linkedin-buying-signals__analyze_prospects",
"mcp__linkedin-buying-signals__draft_email",
"mcp__linkedin-buying-signals__draft_linkedin_message",
"mcp__linkedin-buying-signals__mark_email_sent",
"mcp__linkedin-buying-signals__create_custom_signal"
],
"deny": [
"mcp__linkedin-buying-signals__send_email",
"mcp__linkedin-buying-signals__send_linkedin_message"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as linkedin-buying-signals. Review it before you use it.
Capability tags behind 6 rules
- mcp__linkedin-buying-signals__get_prospect private-data, untrusted-input
- mcp__linkedin-buying-signals__get_pipeline_stats private-data, untrusted-input
- mcp__linkedin-buying-signals__find_leads_from_signals untrusted-input
- mcp__linkedin-buying-signals__send_email outbound
- mcp__linkedin-buying-signals__send_linkedin_message outbound
- mcp__linkedin-buying-signals__mark_email_sent outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.getcleed/linkedin-buying-signals/verify?hash=1b011a35e0fdf2b21d8ba75a07c889f7bd1063c8f91ed7605c54611609e49cc8" | jq -e '.changed == false'Pinned hash 1b011a35e0fd, from Nov 10, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.getcleed/linkedin-buying-signals/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.getcleed/linkedin-buying-signals)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:55 UTC.
linkedin-buying-signals MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the linkedin-buying-signals MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 10 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the linkedin-buying-signals MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: send_email and send_linkedin_message.
Can the linkedin-buying-signals MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the linkedin-buying-signals MCP server have?
- 16 tools: 2 destructive, 8 write, 6 read. send_email, send_linkedin_message, add_leads_from_urls, find_leads_from_signals, import_sourced_leads, analyze_prospects, draft_email, draft_linkedin_message and 8 more.
Does the linkedin-buying-signals MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the linkedin-buying-signals MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_email, send_linkedin_message and mark_email_sent.
Has the linkedin-buying-signals MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.