@larsbaunwall/unlinked

MCPattested
v2.0.0Lars BaunwallMITUpdated 6d agonpmGitHub

Your LinkedIn profile as JSON from the command line, and as an MCP server for AI assistants like Claude Desktop and GitHub Copilot.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
97Downloads/wk
4GitHub stars
6d agoLast update
Needs 1 credential before it runs
  • LINKEDIN_TOKENAPI keyrequired

    LinkedIn access token from the OAuth Token Generator. Accepts a bare token or 'Bearer <token>'. Required for EEA/Switzerland members only.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorLars Baunwall
LicenseMIT
Version2.0.0
Sourcenpm+mcp-registry
npm@larsbaunwall/unlinked
GitHublarsbaunwall/Unlinked
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · a54c522
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv2.0.0 · todayHow well does this scan work?
EvalsNone
IndexedOct 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Statically extracted from the published packagev2.0.0 · 3h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

linkedin_get_profileGet the user's LinkedIn résumé in one call, with their latest edits already included: Intro and About, Experience, Education, Skills, Licenses & certifications and Projects by default.

Get the user's LinkedIn résumé in one call, with their latest edits already included: Intro and About, Experience, Education, Skills, Licenses & certifications and Projects by default.

No input schema was published for this tool.

linkedin_get_sectionGet one section of the user's LinkedIn data a page at a time, newest first, with their latest changes already included.

Get one section of the user's LinkedIn data a page at a time, newest first, with their latest changes already included.

No input schema was published for this tool.

linkedin_get_recent_activityGet what changed on the user's LinkedIn in the last 28 days, newest first: profile edits, new posts, comments and reactions.

Get what changed on the user's LinkedIn in the last 28 days, newest first: profile edits, new posts, comments and reactions.

No input schema was published for this tool.

linkedin_check_accessCheck whether LinkedIn is sharing the user's recent changes with this app. Use it to diagnose missing recent activity or access errors before retrying other tools.

Check whether LinkedIn is sharing the user's recent changes with this app. Use it to diagnose missing recent activity or access errors before retrying other tools.

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Your LinkedIn profile as JSON from the command line, and as an MCP server for AI assistants like Claude Desktop and GitHub Copilot.

Keywords
mcplinkedinmodel-context-protocolaiprofessional-profile
Alternatives
Comparing tool surfaces…

Tools exposed

4 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-13 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in social media