ToolTrust
C32/100
Smithery

linkmcp-linkmcp

mcpsmithery

@Smithery

Hosted MCP server for LinkedIn. 25 tools: profiles, messages, search, post engagement, company data, enrichment. Works with Claude, ChatGPT, Cursor, Windsurf, n8n, Make. OAuth authentication, rate limited, account-safe.

By Smithery | 81 findings | Scanned 4/19/2026 | tooltrust-scanner/v0.3.8

20 High17 Medium19 Low25 Info

Risk Summary

Needs Approval

Excessive Permissions plus Dep Visibility raises enough risk that this tool should not be auto-trusted.

Potential impact: The agent may gain overly broad access to files, network, databases, or execution capabilities.

Recommended action: Keep this tool behind manual approval and avoid unattended runs until the risky capabilities are narrowed or removed.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (81)

  • HighAS-002

    ⚠️Excessive Permissions ×19

    tool declares network permission

    linkedin_get_companylinkedin_get_company_postslinkedin_get_connectionslinkedin_get_person_postslinkedin_get_post_commentslinkedin_get_post_reactionslinkedin_bulk_get_profileslinkedin_get_profilelinkedin_bulk_get_companieslinkedin_list_connection_requestslinkedin_send_connection_requestlinkedin_react_to_postlinkedin_respond_connection_requestlinkedin_create_postlinkedin_comment_on_postlinkedin_search_peoplelinkedin_search_sales_navigatorfind_mobilelinkedin_who_am_i

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • HighAS-010

    🔑Insecure Secret Handling

    linkedin_respond_connection_request:input parameter "shared_secret" appears to accept a secret or credential

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

  • MediumAS-002

    ⚠️Excessive Permissions ×17

    tool declares fs permission

    linkedin_get_companylinkedin_get_connectionslinkedin_get_person_postslinkedin_get_post_commentslinkedin_get_post_reactionslinkedin_bulk_get_profileslinkedin_get_profilelinkedin_bulk_get_companieslinkedin_list_connection_requestslinkedin_send_connection_requestlinkedin_create_postlinkedin_comment_on_postlinkedin_search_peoplelinkedin_search_sales_navigatorfind_emailfind_mobilelinkedin_who_am_i

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×19

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    linkedin_get_companylinkedin_get_company_postslinkedin_get_connectionslinkedin_get_person_postslinkedin_get_post_commentslinkedin_get_post_reactionslinkedin_bulk_get_profileslinkedin_get_profilelinkedin_bulk_get_companieslinkedin_list_connection_requestslinkedin_send_connection_requestlinkedin_react_to_postlinkedin_respond_connection_requestlinkedin_create_postlinkedin_comment_on_postlinkedin_search_peoplelinkedin_search_sales_navigatorfind_mobilelinkedin_who_am_i

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×25

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    linkedin_get_companylinkedin_get_company_postslinkedin_get_connectionslinkedin_get_person_postslinkedin_get_post_commentslinkedin_get_post_reactionslinkedin_bulk_get_profileslinkedin_get_profilelinkedin_bulk_get_companieslinkedin_list_connection_requestslinkedin_send_connection_requestlinkedin_react_to_postlinkedin_respond_connection_requestlinkedin_create_postsend_feedbacklinkedin_comment_on_postlinkedin_send_messagelinkedin_search_peoplelinkedin_search_sales_navigatorlinkedin_list_conversationslinkedin_get_conversation_messagesfind_emailfind_mobilevalidate_emaillinkedin_who_am_i

    Fix: Review and remediate the identified issue.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y linkmcp-linkmcp"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade C](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-c.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)