linkedin-buying-signals
Find B2B prospects showing buying signals on LinkedIn and draft the outreach
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: find leads.Similar tools
Listed for the same task: find leadsReviews
No review yet. Used linkedin-buying-signals? Be the first to help others choose.What it does
linkedin-buying-signals is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to 3 capabilities: lead generation, outreach sequencing and social media management. That makes it a candidate for tasks such as find leads or find B2B partners.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 13h ago (live check)Hosted endpoint
https://www.getcleed.com/api/mcpstreamable-http
In Claude Code: claude mcp add --transport http linkedin-buying-signals https://www.getcleed.com/api/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"linkedin-buying-signals": {
"url": "https://www.getcleed.com/api/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 13h agoONLINE linkedin-buying-signals answered an MCP connection on 16 Nov 2026 and introduced itself as getcleed 1.0.0 (MCP protocol 2025-06-18).
38 tools offered to AI assistants
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 Getcllist_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 signalget_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 targeting (ICP): target roles, industries, countries, company sizes, relevant keywords and every saved exclusion. This is what find_leads searches for and what scoring filters against. Change it with update_targeting, add_exclusiadd_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,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: expdraft_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 chara
Show 26 more
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 undsend_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 LinkedInmark_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.find_leads· Search for a few new people (5 by default, up to 50) matching the account targeting (see get_icp; change it with update_targeting or add_exclusion first if the user wants someone else). Runs in the background for two to five minutes and putget_search_status· Whether a find_leads search is running or finished, how many people are waiting in the review queue per search, and the weekly discovery allowance left.list_search_results· People found by searches, best fit first. "to_review" is the queue waiting for a decision, "approved" the ones saved as leads, "rejected" the ones marked not a fit (they can be restored with reject_leads undo). Each person has a fit level aapprove_leads· Save people from the review queue as leads (in a list named after their search), and optionally add them to a sequence. Pass ids from one search, or a searchId to approve everyone still waiting in it. If the sequence is running, the first creject_leads· Mark people in the review queue as not a fit, optionally with the reason. They leave the queue and later searches skip them. With undo: true, brings rejected people back to the queue. When the reason would apply to others too, offer add_excupdate_targeting· Change who find_leads looks for: target job titles, industries, countries and company sizes. Each field passed replaces that field; fields left out stay as they are. Show the user the current targeting (get_icp) and the change before callinadd_exclusion· Save an exclusion in the account targeting so later searches skip matching people: a job title keyword, an industry, or a company size limit. With candidateId (a result just rejected), matching people still waiting in that same search are rremove_exclusion· Take one saved exclusion out of the account targeting. Pass it as get_icp lists it under exclusions.list_sequences· Every outreach sequence in the account: whether it is running, whether each message is reviewed before sending, its steps in short, and how many leads are in each state.get_sequence· One sequence in full: its steps, its sections (the search each group of leads came from, which can be stopped or resumed on its own), and each lead with where they are, what happens next and when.create_sequence· Create an outreach sequence. approach "signal": a connection request, then an opener Getcleed writes for each lead from their own signals and two follow-ups (the default, and what the product is for). "simple": four short generic messages.add_leads_to_sequence· Put saved leads (prospect ids from list_prospects) into a sequence. Leads already in a sequence, dismissed, or who replied are skipped. If the sequence is running, the first call returns what will be sent and needs confirm: true. Without Listart_sequence· Start a sequence: its leads are enrolled and steps begin going out on the sending schedule, from the user's own LinkedIn account. The first call returns how many people it reaches and whether messages are reviewed first; it only starts withstop_sequence· Stop a running sequence: nothing more is sent until it is started again. With section, stops only the leads that came from that search and leaves the rest running. Stopping never unsends anything.list_sequence_messages· For each lead in a sequence, the messages still to be sent to them, with the text when it is already written, and the evidence about the lead the text is based on. Use it to show the user what will go out, and before approving a message wheupdate_sequence_lead· Act on one lead inside a sequence (enrollmentId from get_sequence or list_sequence_messages). editText rewrites a message not sent yet. status "active" approves the waiting message when review is on (pass the evidenceFingerprint that list_slist_replies· Conversations where a lead answered the outreach and the user has not replied yet, newest first, on LinkedIn and by email. Use the id and channel with get_conversation and send_reply.get_conversation· The messages of one conversation with a lead, oldest first, each marked as written by the user or by the lead. Read it before writing a reply.send_reply· Send a reply in a conversation, from the user's own LinkedIn account or mailbox. It reaches the lead immediately and cannot be undone: show the user the exact text and get their agreement first. Only conversations started by Getcleed outreaget_account_status· Where the account stands: plan and allowances, whether the targeting exists, whether LinkedIn and a mailbox are connected, the sending schedule, and the next steps the product suggests. Steps that need a browser (connecting LinkedIn or a maupdate_sending_settings· When and how fast sequences send: time zone, days, hours, daily limits, and whether sending is on at all. Fields left out keep their value. Turning it on lets running sequences send: that first call returns the schedule and needs confirm: tset_lead_status· Dismiss saved leads (prospect ids from list_prospects): no more outreach goes to them and any sequence they are in is paused for them. "restored" brings dismissed leads back.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://www.getcleed.com/api/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://www.getcleed.com/claude | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/nossa-y/hp-auto-deploy | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.1.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is linkedin-buying-signals still online?
Free alerts · no account▲ 0Do you run linkedin-buying-signals? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about linkedin-buying-signals
How do I connect linkedin-buying-signals?
Use the hosted endpoint https://www.getcleed.com/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does linkedin-buying-signals offer?
When Electra Index connected on 16 Nov 2026, it listed 38 tools: get_sample_pipeline, list_prospects, get_prospect, get_pipeline_stats, list_signals, get_icp, add_leads_from_urls, find_leads_from_signals and more. The full list is in "Live check" above.
Is linkedin-buying-signals online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 13h ago.
What can I use linkedin-buying-signals for?
Based on its description, it is most relevant to: find leads, find B2B partners, send personalized outreach, recruit developers.