LinkedIn MCP Server (Salesbot)
REMOTE · APP.SALESBOT.CZ · SCANNED SEP 20
Human-in-the-loop LinkedIn outreach and a built-in sales CRM for AI agents. Safety-gated, anti-spam.
Available components
Recent critical change
Authorization (9 Aug 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (stop_campaign). See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8488 tokens (~136/item across 62 items; 62 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% 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 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 62 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the LinkedIn MCP Server (Salesbot) server?
LinkedIn MCP Server (Salesbot) is a hosted endpoint at https://app.salesbot.cz/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 · app.salesbot.cz
claude mcp add --transport http cz-salesbot-linkedin-mcp-server 'https://app.salesbot.cz/api/mcp'
{
"mcpServers": {
"cz-salesbot-linkedin-mcp-server": {
"url": "https://app.salesbot.cz/api/mcp"
}
}
} {
"servers": {
"cz-salesbot-linkedin-mcp-server": {
"type": "http",
"url": "https://app.salesbot.cz/api/mcp"
}
}
} [mcp_servers.cz-salesbot-linkedin-mcp-server] url = "https://app.salesbot.cz/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cz-salesbot-linkedin-mcp-server": {
"type": "remote",
"url": "https://app.salesbot.cz/api/mcp",
"enabled": true
}
}
} openclaw mcp add cz-salesbot-linkedin-mcp-server --url 'https://app.salesbot.cz/api/mcp' --transport streamable-http
mcp_servers:
cz-salesbot-linkedin-mcp-server:
url: "https://app.salesbot.cz/api/mcp" {
"McpServers": {
"cz-salesbot-linkedin-mcp-server": {
"Transport": "http",
"Url": "https://app.salesbot.cz/api/mcp"
}
}
} assistant mcp add cz-salesbot-linkedin-mcp-server -t streamable-http -u 'https://app.salesbot.cz/api/mcp'
{
"mcpServers": {
"cz-salesbot-linkedin-mcp-server": {
"type": "http",
"url": "https://app.salesbot.cz/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.
- 19 Sept 26 0
- New tool “remove_contacts_from_list” functional
- 16 Sept 26 0
- Tool “search_linkedin_people” rewrote its description, which is the text the model reads security
- 11 Sept 26 0
- Tool “update_campaign_settings” rewrote its description, which is the text the model reads security
- Tool “get_chat_messages” rewrote its description, which is the text the model reads security
- Tool “get_contact_profile” rewrote its description, which is the text the model reads security
- Tool “get_job_posting_details” rewrote its description, which is the text the model reads security
- Tool “list_campaign_queue” rewrote its description, which is the text the model reads security
- Tool “list_contacts” rewrote its description, which is the text the model reads security
- Tool “list_inbox_chats” rewrote its description, which is the text the model reads security
- Tool “mark_chat_read” rewrote its description, which is the text the model reads security
- Tool “search_google_xray” rewrote its description, which is the text the model reads security
- Tool “search_web” rewrote its description, which is the text the model reads security
- Schema quality: 7427 → 8243 ▼ functional
- New tool “check_blacklist” functional
- New tool “exclude_contacts_from_campaign” functional
- New tool “list_blacklist” functional
- New tool “list_mcp_pending_actions” functional
- New tool “search_crm_leads” functional
- New tool “update_crm_lead” functional
- “search_google_xray” added an optional parameter “jobTitles” cosmetic
- “search_google_xray” reworded the description of “jobTitle” cosmetic
- “search_linkedin_people” reworded the description of “location” cosmetic
- “search_linkedin_people” reworded the description of “locationId” cosmetic
- “search_google_xray” made “jobTitle” optional cosmetic
- 10 Sept 26 +2
- The server changed its declared name: salesagent-mcp → salesbot security
- Tool “add_contacts_to_campaign” rewrote its description, which is the text the model reads security
- Tool “get_daily_limits” rewrote its description, which is the text the model reads security
- Tool “search_job_postings” rewrote its description, which is the text the model reads security
- Tool “search_linkedin_people” rewrote its description, which is the text the model reads security
- Tool “send_connection_request” rewrote its description, which is the text the model reads security
- Tool “send_linkedin_message” rewrote its description, which is the text the model reads security
- Schema quality: unverified → 100 ▲ functional
- The server now declares the “prompts” capability functional
- New prompt “salesbot_campaign_operator” functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “create_lead_list” functional
- New tool “list_campaign_queue” functional
- New tool “prepare_campaign_messages” functional
- “reject_message” added an optional parameter “regenerate” cosmetic
- “search_linkedin_people” added an optional parameter “decisionMakers” cosmetic
- “search_linkedin_people” added an optional parameter “departments” cosmetic
- “send_linkedin_message” added an optional parameter “contact_id” cosmetic
- “search_linkedin_people” reworded the description of “titles” cosmetic
- “send_connection_request” made “linkedin_id” optional cosmetic
- “send_connection_request” made “profile_id” optional cosmetic
- “send_linkedin_message” made “linkedin_id” optional cosmetic
- “send_linkedin_message” made “profile_id” optional cosmetic
- 9 Sept 26 0
- Tool “sync_linkedin_connections” rewrote its description, which is the text the model reads security
- “search_linkedin_people” reworded the description of “companyId” cosmetic
- “sync_linkedin_connections” reworded the description of “limit” cosmetic
- 8 Sept 26 0
- Stability: 0.97 → pass security
- Tool “add_contacts_to_campaign” rewrote its description, which is the text the model reads security
- Tool “create_campaign” rewrote its description, which is the text the model reads security
- Tool “search_linkedin_navigator” rewrote its description, which is the text the model reads security
- Tool “search_linkedin_people” rewrote its description, which is the text the model reads security
- New tool “sync_linkedin_connections” functional
- “search_google_xray” added an optional parameter “list_id” cosmetic
- “search_linkedin_navigator” added an optional parameter “cursor” cosmetic
- “search_linkedin_people” added an optional parameter “connectionsOnly” cosmetic
- “search_linkedin_people” added an optional parameter “keywords” cosmetic
- “search_linkedin_navigator” reworded the description of “limit” cosmetic
- “search_linkedin_people” reworded the description of “company” cosmetic
- “search_linkedin_people” reworded the description of “companyId” cosmetic
- “search_linkedin_people” reworded the description of “limit” cosmetic
- “search_linkedin_people” reworded the description of “location” cosmetic
- “search_linkedin_people” reworded the description of “locationId” cosmetic
- “search_linkedin_people” reworded the description of “network” cosmetic
- “search_linkedin_people” reworded the description of “titles” cosmetic
- 7 Sept 26 0
- Tool “search_linkedin_people” rewrote its description, which is the text the model reads security
- Stability: pass → 0.97 functional
- New tool “add_contacts_to_list” functional
- “upsert_linkedin_contact” added an optional parameter “list_id” cosmetic
- 5 Sept 26 0
- Tool “upsert_linkedin_contact” rewrote its description, which is the text the model reads security
- “upsert_linkedin_contact” added an optional parameter “personalization_note” cosmetic
- “upsert_linkedin_contact” added an optional parameter “web_research” cosmetic
- “search_linkedin_people” reworded the description of “titles” cosmetic
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 20 Sept 2026 · Probed https://app.salesbot.cz/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.salesbot.cz | CN=YR1,O=Let's Encrypt,C=US | 11 Aug 2026 | 9 Nov 2026 | RSA 2048 | SHA256-RSA | 56193de16b3eb45655e93b4ca08df5577dd |
| SANs: app.salesbot.cz | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 app.salesbot.cz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cz. | present | 20237 | 13 | Verified |
| salesbot.cz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.salesbot.cz/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.salesbot.cz/api/mcp | HTTPS enforced | 308 | https://app.salesbot.cz/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 →
search_web ~208
General-purpose Google search — returns organic results for any query. Unlike search_google_xray (LinkedIn-only), this searches the entire web. Useful for finding job postings on portals (jobs.cz, prace.cz, profesia.sk, indeed.com), company info, news, or any other web content. Results are NOT saved to contacts — use this for research and discovery. Capped at 4 calls per minute to protect the Serper/Google budget.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country code for localized results (e.g. 'cz', 'sk', 'de', 'us'). Default: 'cz'. |
| language | string | – | Language code (e.g. 'cs', 'sk', 'en', 'de'). Default: 'cs'. |
| limit | number | – | Max results (1-30, default 10) |
| query | string | yes | Google search query. Use operators like site:jobs.cz, intitle:, OR, quotes for exact match, etc. |
No output schema declared.
No examples provided.
send_connection_request ~110
Send a LinkedIn connection invitation. Prefer contact_id; Salesbot resolves the LinkedIn identifier internally. The invitation is ALWAYS empty (no text). Daily/hourly limits, allowed hours, blacklist, random delays and human approval are enforced.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | – | UUID of the contact in DB (for blacklist check). Optional. |
| linkedin_id | string | – | LinkedIn public ID of the person to connect with |
| profile_id | string | – | UUID of the user_profile to send from |
No output schema declared.
No examples provided.
send_linkedin_message ~137
Send a one-off LinkedIn message to a specific saved contact outside any campaign. Prefer contact_id; Salesbot resolves the LinkedIn identifier internally. A random delay, daily/hourly limits, allowed hours and human approval are enforced.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | – | Preferred: Salesbot contact UUID. Used to resolve linkedin_id safely. |
| linkedin_id | string | – | LinkedIn public ID of the recipient (e.g. 'jan-novak-12345') |
| message | string | yes | Message text to send (max 5000 chars) |
| profile_id | string | – | UUID of the user_profile to send from |
No output schema declared.
No examples provided.
set_deal_stage ~143
Move a lead to a different pipeline stage. Stages are user-configurable — call list_crm_stages to see the valid stage keys (defaults: prospect, contacted, demo, won, lost). Call when the user confirms a real-world event in plain English ('they booked a demo', 'we won this deal'). Logs who changed it and an optional note to the deal history.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | UUID of the contact/lead |
| note | string | – | Optional context for the history log. |
| stage | string | yes | Target stage key (see list_crm_stages; defaults: prospect/contacted/demo/won/lost). |
No output schema declared.
No examples provided.
set_lead_fields ~96
Set custom field values on a lead (by contact_id). Pass `fields` as an object of { field_key: value }. Only defined field keys are accepted (see list_crm_fields). Adds the lead to the CRM if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | UUID of the contact. |
| fields | object | yes | Object mapping custom field keys to values, e.g. { "budget": 5000 }. |
No output schema declared.
No examples provided.
start_campaign ~73
Start (activate) an existing campaign: schedules the outreach actions for its contacts and sets status to 'running'. The campaign must already have contacts (add_contacts_to_campaign) and steps. Execution still respects daily limits, allowed hours and anti-detection delays.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | UUID of the campaign to start |
No output schema declared.
No examples provided.
stop_campaign ~63
Stop a running campaign: sets status to 'stopped' and cancels its pending scheduled actions (a DB trigger marks them skipped). To only pause temporarily, use update_campaign_settings with status='paused'.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | UUID of the campaign to stop |
No output schema declared.
No examples provided.
sync_linkedin_connections ~155
Synchronize one provider-safe page (at most 500) of the API-key owner's 1st-degree LinkedIn relations into the local workspace cache. This is a provider read, not a LinkedIn people search, and does not consume the search quota. The server persists continuation state and atomically enforces a 15–20 minute delay, four-page hourly cap, and twelve-page daily cap across UI and MCP. Respect RELATIONS_SYNC_PROTECTED retry_after_seconds before continuing.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Continuation cursor returned by the previous sync page. |
| limit | number | – | Relations per page (1-500, default 500). |
| sync_id | string | – | Sync ID returned with the continuation cursor. |
No output schema declared.
No examples provided.
update_campaign_settings ~177
Update settings of an existing campaign you own: name, description, daily_limit, sender_context, auto_approve_messages, or status. status='paused' cancels pending actions safely. status='running' performs a real resume through start_campaign and recreates only the interrupted active steps; excluded contacts remain excluded. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_approve_messages | boolean | – | Whether AI drafts are auto-approved. Optional. |
| campaign_id | string | yes | UUID of the campaign |
| daily_limit | number | – | New daily action limit. Optional. |
| description | string | – | New description. Optional. |
| name | string | – | New name. Optional. |
| sender_context | string | – | New sender context for the AI. Optional. |
| status | string | – | New status (e.g. paused/running). Optional. |
No output schema declared.
No examples provided.
update_contact ~143
Update a lead's contact details — email, phone, location, company, position or headline. Use to enrich a lead (e.g. save an email address you found). Only the fields you pass are changed; omit the rest. Does not create contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name. Optional. |
| contact_id | string | yes | UUID of the contact |
| string | – | Email address. Optional. | |
| headline | string | – | LinkedIn-style headline. Optional. |
| location | string | – | City / location. Optional. |
| phone | string | – | Phone number. Optional. |
| position | string | – | Job title / position. Optional. |
No output schema declared.
No examples provided.
update_crm_lead ~190
Update a CRM lead by contact_id or crm_lead_id. Sets pipeline stage, deal value and/or contact details in one tenant-scoped call. Only supplied fields change; stage changes are added to the audit history.
| Name | Type | Req | Description |
|---|---|---|---|
| clear_deal_value | boolean | – | Set deal value to null. |
| company | string | – | – |
| contact_id | string | – | Contact UUID. Use this when available. |
| crm_lead_id | string | – | CRM lead UUID returned by search_crm_leads. |
| deal_value | number | – | Non-negative deal value. |
| string | – | – | |
| headline | string | – | – |
| location | string | – | – |
| note | string | – | Optional note stored with a stage change. |
| phone | string | – | – |
| position | string | – | – |
| stage | string | – | Pipeline stage key returned by list_crm_stages. |
No output schema declared.
No examples provided.
upsert_linkedin_contact ~341
Create a contact from a known LinkedIn profile URL, or return the existing contact when the profile was already imported. Use this when you already know the exact profile URL and do not need to run a search. The contact is saved to a dedicated CRM Imports list and can then be passed to add_contacts_to_campaign. Pass `web_research` (what you found about their company/person online) and `personalization_note` (a hook for the outreach message) — both are stored on the contact and fed to the LinkedIn message generator as facts to personalize on. On an existing contact these are MERGED in (they enrich, never blank out existing data).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Current company. Optional. |
| full_name | string | – | Contact name. Optional when it is not available yet. |
| headline | string | – | LinkedIn headline. Optional. |
| list_id | string | – | UUID of an existing lead list to put the contact into (from list_lead_lists). Optional — defaults to the 'CRM Imports' list. For an existing contact this MOVES it into that list. |
| personalization_note | string | – | A short note/hook for writing the LinkedIn message (e.g. 'reference their new plant in Brno'). Fed to the message generator. Optional. |
| position | string | – | Current role/title. Optional. |
| profile_url | string | yes | LinkedIn profile URL in the form https://www.linkedin.com/in/... |
| web_research | string | – | Free-text research about the person/company found online (news, website, recent events). Used as facts to personalize the outreach. Optional. |
No output schema declared.
No examples provided.
What is the LinkedIn MCP Server (Salesbot) server?
LinkedIn MCP Server (Salesbot) is listed in the public MCP registry as cz.salesbot/linkedin-mcp-server. Human-in-the-loop LinkedIn outreach and a built-in sales CRM for AI agents. Safety-gated, anti-spam. This page covers its hosted endpoint (https://app.salesbot.cz/api/mcp).
Is the LinkedIn MCP Server (Salesbot) server safe to use?
LinkedIn MCP Server (Salesbot) 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 LinkedIn MCP Server (Salesbot) server expose?
LinkedIn MCP Server (Salesbot) exposes 62 tools: search_linkedin_people, sync_linkedin_connections, search_google_xray, upsert_linkedin_contact, add_contacts_to_list, and 57 more. Their descriptions and schemas cost roughly 8,488 tokens of context every time the server is loaded.
Does the LinkedIn MCP Server (Salesbot) server require authentication?
No. We connected to LinkedIn MCP Server (Salesbot) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LinkedIn MCP Server (Salesbot) server still maintained?
LinkedIn MCP Server (Salesbot) is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.