MCP.Market

Linkedin MCP server

online · 100% uptime
by veezee.io·io.veezee/linkedin·v3.1.0
No reviews yet

LinkedIn data for AI agents: search, profiles, companies, posts. Free key, self-minted, no signup.

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Linkedin yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Linkedin tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 333ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 66 days ago12/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Linkedin compares

Against every graded Sales and outbound MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 80% of 877 Sales and outbound servers
Uptime
100%
of our recent checks; the typical remote Sales and outbound server answers 100%
Response time
178 ms
faster than 72% of 672 Sales and outbound servers

Install Linkedin in Claude Code, Cursor or VS Code

claude mcp add --transport http linkedin https://mcp.veezee.io/linkedin
Add to Cursor

What the publisher says

From the Linkedin repository's README, as published. We do not edit it. Read it on GitHub

Veezee MCP server

LinkedIn, Reddit, and X (formerly Twitter) data for AI agents, over MCP or REST. This repo is the public home and issue tracker for the hosted servers on the official MCP Registry: io.veezee/linkedin (3.1.0), io.veezee/reddit (1.1.0), and io.veezee/x-twitter (1.1.0). The server is a hosted service; this repo also ships a small stdio proxy (npx github:veezeehq/veezee-mcp) for clients that spawn a local command.

  • Every call needs a free key, and minting one costs nothing: no signup, no card, no human. See Quickstart below. The free tier is 200 credits per IP per day across all platforms, cached data, first page only. Paying at https://veezee.io/upgrade credits the same key with a higher budget, realtime freshness, and full pagination.
  • Website and docs: https://veezee.io
  • Found a bug or a gap? Open an issue or write hello@veezee.io.

Run locally (stdio)

For MCP clients that spawn a local command instead of connecting to a URL:

npx github:veezeehq/veezee-mcp

The proxy connects to https://mcp.veezee.io/all and mints a free trial key on first run (no signup). Set VEEZEEAPIKEY to reuse one key across runs, and VEEZEEMCPURL to point at a single-platform mount. Docker: docker build -t veezee-mcp . && docker run -i veezee-mcp.

Mounts

Four endpoints, all streamable-http, same auth and pricing:

Pick a single-platform mount when your agent only needs one platform: a smaller tool list is easier for the model to pick from correctly and costs less context per turn. Pick /all when one task spans platforms, e.g. a research brief that pulls LinkedIn, Reddit, and X signal on the same account, or a monitoring loop that watches more than one platform at once.

The 17 tools

LinkedIn (https://mcp.veezee.io/linkedin)

Reddit (https://mcp.veezee.io/reddit)

X, formerly Twitter (https://mcp.veezee.io/x)

Every mount

Any tool call can set freshness: "realtime" for +2 credits to force a live fetch instead of cached data. Full tool reference with schemas: https://veezee.io/docs

Quickstart

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Linkedin: common questions

Is Linkedin MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Linkedin safety report
How do I install Linkedin?
It runs remotely at mcp.veezee.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Linkedin need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Linkedin maintained?
The last commit was 104 days ago (2026-07-21). The latest release is v3.1.0.
Is Linkedin up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Linkedin?
Servers from other publishers that do the same job: Linkedin Data MCP server, Postbase MCP server and LinkedIn Toolkit MCP server.
How does Linkedin compare with other Sales and outbound MCP servers?
safety score 88/100 (higher than 80% of 877 Sales and outbound servers); uptime 100% (of our recent checks; the typical remote Sales and outbound server answers 100%); response time 178 ms (faster than 72% of 672 Sales and outbound servers). Full comparison.

Alternatives to Linkedin

Same job from other publishers: the closest match first, then the best rated.

  • Linkedin Data
    superagnt: marketing plugin for Claude and ChatGPT. Know your market: LinkedIn profiles and posts.
    A
  • Postbase
    Schedule social posts, threads and video to X, LinkedIn, Bluesky, Mastodon and YouTube from your AI.
    A
  • LinkedIn Toolkit
    LinkedIn for AI agents from your own Chrome session: search, profiles, lists, outreach queue.
    A
  • Chirpie
    Post, schedule, and track social posts on X, Bluesky, LinkedIn, Instagram and more from AI agents.
    A
  • LinkFetch: LinkedIn MCP
    LinkedIn jobs, companies and people for AI agents, plus messages and invites via your own account.
    A

More from veezee.io →