Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"unlinked": {
"env": {
"LINKEDIN_TOKEN": "<your_access_token>"
},
"args": [
"-y",
"@larsbaunwall/unlinked"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Bring your LinkedIn professional profile into AI assistants — without copy-pasting, scraping, or guessing.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Autonomous spec-to-product coding-agent CLI with an MCP server exposing 34 tools over stdio.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
App framework, testing framework, and inspector for MCP Apps.
MCP Security Weekly
Get CVE alerts and security updates for io.github.larsbaunwall/unlinked and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Bring your LinkedIn professional profile into AI assistants — without copy-pasting, scraping, or guessing.
Unlinked is a TypeScript MCP server that connects your LinkedIn professional profile and experience to any Model Context Protocol client — Claude Desktop, GitHub Copilot, and others. It reads your data directly from LinkedIn's official Member Data Portability API, so your assistant always has accurate, up-to-date context about who you are professionally.
:eu: EEA / Switzerland only. LinkedIn's Member Data Portability API is currently available exclusively to members located in the European Economic Area and Switzerland. Thank you, Digital Markets Act (DMA)!
Once connected, your AI assistant can:
All data access is read-only. Your access token is used only to talk to LinkedIn and is never stored, logged, or echoed back.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"unlinked": {
"command": "npx",
"args": ["-y", "@larsbaunwall/unlinked"],
"env": {
"LINKEDIN_TOKEN": "<your_access_token>"
}
}
}
}
The config file is typically at:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd to your user-level MCP config (File → Preferences → MCP Servers) or a workspace .vscode/mcp.json:
{
"servers": {
"unlinked": {
"command": "npx",
"args": ["-y", "@larsbaunwall/unlinked"],
"env": {
"LINKEDIN_TOKEN": "<your_access_token>"
}
}
}
}
| Tool | Description |
|---|---|
linkedin_get_profile | Get the user's LinkedIn résumé: bio, work history, education, skills, certifications, projects, etc. |
linkedin_get_activity | Get the user's LinkedIn activity: connections, posts, articles, comments, likes, job applications |
linkedin_get_section | Get raw data for one specific LinkedIn section by exact name |
linkedin_get_recent_changes | Get recent changes to the user's LinkedIn data (past 28 days), with cursor-based polling |
linkedin_check_access | Check whether the user has granted LinkedIn data access — useful for diagnosing missing data |
| Environment variable | Required | Description |
|---|---|---|
LINKEDIN_TOKEN | Yes | LinkedIn access token. Accepts Bearer <token> or a bare token. |
LINKEDIN_API_VERSION | No | API version in YYYYMM format. Defaults to 202312. |
npm install
npm run build
npm run dev # run directly from source with .env
npm run inspect # test with MCP Inspector
See AGENTS.md for implementation guidance.
MIT