linkedin-toolkit-mcp

MCPcommunity
v2.1.0io.github.FormatixAIMITUpdated 16d agonpmGitHub

MCP server, localhost bridge, HTTP action API, SQLite mirror and lit CLI for LinkedIn Toolkit.

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
142Downloads/wk
8GitHub stars
4Forks
16d agoLast update
Package
Authorio.github.FormatixAI
LicenseMIT
Version2.1.0
Sourcenpm+mcp-registry
npmlinkedin-toolkit-mcp
GitHubOpenRecruiterTools/linkedin-toolkit
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · 2 privileged
Security scan✓ Cleanv2.0.3 · 24d agoHow well does this scan work?
EvalsNone
IndexedSep 10, 2026

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

Tools

5 tools · 2 privileged
Statically extracted from the published packagev2.0.3 · 24d 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_query_sqlprivilegedNo description published

This tool published no description. Forge does not invent one.

linkedin_syncNo description published

This tool published no description. Forge does not invent one.

source-candidatesSource and shortlist people on LinkedIn from a short brief, saving them to a list.

Source and shortlist people on LinkedIn from a short brief, saving them to a list.

No input schema was published for this tool.

write-openerprivilegedDraft a short, specific connection-request opener for one person.

Draft a short, specific connection-request opener for one person.

No input schema was published for this tool.

triage-inboxTriage recent LinkedIn replies into positive, neutral and negative buckets.

Triage recent LinkedIn replies into positive, neutral and negative buckets.

No input schema was published for this tool.

3 of 5 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

MCP server, localhost bridge, HTTP action API, SQLite mirror and lit CLI for LinkedIn Toolkit.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · 2 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-09-10 — observed resolution, not a publisher declaration.

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

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

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

+61 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