Ad Copy Ai tools for AI agents. Capabilities: generate ad copy, generate variants, create campaign. Built by MEOK AI Labs.
from $12/mo
Nothing to run from here
Linkedin Mcp Tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
LinkedIn MCP server — structured LinkedIn data via a real stealth-browser session. Profiles, search, jobs, companies, messaging, network. Works with Claude, Cursor, and any MCP client.
Quickstart
# 1 — run it from where its publisher ships it
npx -y linkedin-mcp-tools
# 2 — ask your agent something
> LinkedIn MCP server — structured LinkedIn data via a real stealth-browser session. Profiles, search, jobs, companies, messaging, network
Linkedin Mcp Tools is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
DEAll 2 servers
devag72 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Linkedin Mcp Tools as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add linkedin-mcp-tools -- npx -y linkedin-mcp-toolsReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search LinkedIn people by keywords. Returns name, headline, location, and public identifier (pass that to get_profile for full details).
Takes no parameters.
Example callreturns →
Search LinkedIn jobs by keywords (and optional location). Returns title, location, posted time.
Takes no parameters.
Example callreturns →
List your recent LinkedIn messaging conversations (title, last activity, unread count).
Takes no parameters.
Example callreturns →
Get full details for a job posting by its numeric id (the digits in /jobs/view/<id> or from search_jobs jobUrn).
Takes no parameters.
Example callreturns →
Search LinkedIn companies by keywords. Returns name + universalName slug (pass that to get_company for full details).
Takes no parameters.
Example callreturns →
Get a company by its LinkedIn URL slug (e.g.
Takes no parameters.
Example callreturns →
Get a company
Takes no parameters.
Example callreturns →
List employees LinkedIn surfaces for a company (by URL slug). Returns name, headline, and public identifier (feed the slug to get_profile). Prospecting core.
Takes no parameters.
Example callreturns →
List your pending connection invitations — received (inbound, with the urn/sharedSecret to accept later) and sent (outbound). Read-only.
Takes no parameters.
Example callreturns →
Read messages in a LinkedIn conversation by its URN (get the URN from get_inbox).
Takes no parameters.
Example callreturns →
Get recent posts from your LinkedIn home feed (author + post text).
Takes no parameters.
Example callreturns →
Get your recent LinkedIn notifications (headline, time, read state).
Takes no parameters.
Example callreturns →
Get the authenticated user
Takes no parameters.
Example callreturns →
Get a LinkedIn profile by public identifier (the slug in the profile URL, e.g.
Takes no parameters.
Example callreturns →
Report server version, browser/login status, and capabilities.
Takes no parameters.
Example callreturns →
Deep health check: cookie login state, a LIVE Voyager probe (confirms the API actually answers, not just that a cookie exists), and today\
Takes no parameters.
Example callreturns →
Close the browser context and release resources (kills the Chrome process).
Takes no parameters.
Example callreturns →
[ALPHA, write] Send a connection request. Gated: requires confirm:true. Returns a structured status (ok | duplicate | already_connected | restricted | quota_exhausted | failed). Counts against the daily connect cap.
Takes no parameters.
Example callreturns →
[ALPHA, write] Send a message. Pass thread_id / conversation_urn to REPLY into an existing conversation (verified); otherwise a new thread is started to recipient_urn (best-known). Gated: requires confirm:true. Returns a structured status. Counts against the daily message cap.
Takes no parameters.
Example callreturns →
[ALPHA, write] Publish a text post to your feed. Gated: requires confirm:true. Returns a structured status.
Takes no parameters.
Example callreturns →
[ALPHA, write] React to a post. Gated: requires confirm:true. Returns a structured status.
Takes no parameters.
Example callreturns →
[ALPHA, write] Comment on a post. Gated: requires confirm:true. Returns a structured status.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Linkedin Mcp Tools costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 96 / 100
Release 2.0.3 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest3e614b5d1d944e089972e61e1678563fbb3018fcfe431c010c6d6b637f71c950
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (22 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| whoami | no tags | |
| health_check | no tags | |
| close_session | no tags | |
| get_my_profile | no tags | |
| get_profile | no tags | |
| get_feed | no tags | |
| get_notifications | no tags | |
| search_people | no tags | |
| search_jobs | no tags | |
| get_inbox | no tags | |
| get_job_details | no tags | |
| search_companies | no tags | |
| get_company | no tags | |
| get_company_posts | no tags | |
| get_company_employees | no tags | |
| get_pending_invitations | no tags | |
| get_conversation | untrusted-input | |
| connect_with_person | no tags | |
| send_message | external-sink | |
| create_post | no tags | |
| react_to_post | no tags | |
| comment_on_post | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest3e614b5d1d944e08
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 2.0.3 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
2.0.3
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Linkedin Mcp Tools in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.