Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Reach MCP — LinkedIn for AI agents

REMOTE · APP.REACHMCP.COM · SCANNED SEP 20

LinkedIn for AI agents: inbox, invitations, Sales Navigator search, posts. Quotas and webhooks.

Available components

remote · app.reachmcp.com 67
+4 this week 67 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 8304 tokens (~159/item across 52 items; 52 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety98
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 9 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "test_webhook_endpoint" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Reach MCP — LinkedIn for AI agents server?

Reach MCP — LinkedIn for AI agents is a hosted endpoint at https://app.reachmcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.reachmcp.com

# add to Claude Code
claude mcp add --transport http com-reachmcp-linkedin 'https://app.reachmcp.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-reachmcp-linkedin": {
      "url": "https://app.reachmcp.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-reachmcp-linkedin": {
      "type": "http",
      "url": "https://app.reachmcp.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-reachmcp-linkedin]
url = "https://app.reachmcp.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-reachmcp-linkedin": {
      "type": "remote",
      "url": "https://app.reachmcp.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-reachmcp-linkedin --url 'https://app.reachmcp.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-reachmcp-linkedin:
    url: "https://app.reachmcp.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-reachmcp-linkedin": {
      "Transport": "http",
      "Url": "https://app.reachmcp.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-reachmcp-linkedin -t streamable-http -u 'https://app.reachmcp.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-reachmcp-linkedin": {
      "type": "http",
      "url": "https://app.reachmcp.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Sept 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://app.reachmcp.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.reachmcp.com CN=WE1,O=Google Trust Services,C=US 3 Sept 2026 2 Dec 2026 ECDSA 256 ECDSA-SHA256 3e202e71561ad9bb13a015f932479ec5
SANs: app.reachmcp.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.reachmcp.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
reachmcp.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.reachmcp.com/mcp Verified 200
http (plaintext) http://app.reachmcp.com/mcp HTTPS enforced 301 https://app.reachmcp.com/mcp
MCP tools · 52 exposed · ~8,304 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
update_account_quotas ~354

Update one or more quota configuration fields for a LinkedIn account. Only provided fields are updated.

NameTypeReqDescription
account_idintegeryesReach id of the LinkedIn account to act on, from list_accounts.
daily_comments_confinteger–Daily limit for 'comments' on this account; 0 means unlimited.
daily_imports_recruiter_confinteger–Daily limit for 'imports_recruiter' on this account; 0 means unlimited.
daily_imports_salesnav_confinteger–Daily limit for 'imports_salesnav' on this account; 0 means unlimited.
daily_imports_standard_confinteger–Daily limit for 'imports_standard' on this account; 0 means unlimited.
daily_invitations_confinteger–Daily limit for 'invitations' on this account; 0 means unlimited.
daily_messages_confinteger–Daily limit for 'messages' on this account; 0 means unlimited.
daily_posts_confinteger–Daily limit for 'posts' on this account; 0 means unlimited.
daily_reactions_confinteger–Daily limit for 'reactions' on this account; 0 means unlimited.
daily_visits_confinteger–Daily limit for 'visits' on this account; 0 means unlimited.
idempotency_keystring–Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedI…
NameTypeReqDescription
account_idinteger––
quotasobject––
updatedboolean––

No examples provided.

update_scheduled_post ~207

Update the text and/or scheduled time of an existing scheduled LinkedIn post. post_urn is the URN returned by list_scheduled_posts (e.g. urn:li:ugcPost:…). At least one of text or scheduled_at must be provided.

NameTypeReqDescription
account_idintegeryesReach id of the LinkedIn account to act on, from list_accounts.
idempotency_keystring–Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedI…
post_urnstringyesURN of the scheduled post (urn:li:…), from list_scheduled_posts.
scheduled_atinteger–Unix timestamp in milliseconds.
textstring–Plain text to send or post.
NameTypeReqDescription
post_urnstring––
updatedboolean––

No examples provided.

update_webhook_endpoint ~242

Change a webhook's url, events, account_ids, description or is_active. Only provided fields change. Re-enabling clears the failure counter.

NameTypeReqDescription
account_idsarray–Only these LinkedIn account ids; omit for every account of the user.
descriptionstring–Free-text label for your own reference.
endpoint_idintegeryesWebhook endpoint id, from list_webhook_endpoints.
eventsarray–Event types to subscribe to (message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached) or ['*'].
idempotency_keystring–Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedI…
is_activeboolean–Pause (false) or resume (true) deliveries.
urlstring–https URL that receives the signed JSON POST (http accepted for localhost only).
NameTypeReqDescription
account_idsarray|null––
consecutive_failuresinteger––
created_atstring––
descriptionstring––
disabled_reasonstring––
eventsarray––
idinteger––
is_activeboolean––
last_delivery_atstring––
urlstring––

No examples provided.

upload_media_from_url ~209

Upload an image to LinkedIn by fetching it from a public URL. Returns a digitalmediaAsset URN (urn:li:digitalmediaAsset:…) that can be passed to create_post (single image) or create_multi_photo (multi-photo). Use this instead of upload-media when working as an agent — no binary file upload needed.

NameTypeReqDescription
account_idintegeryesReach id of the LinkedIn account to act on, from list_accounts.
idempotency_keystring–Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedI…
image_urlstringyesPublicly accessible URL of the image to upload.
media_upload_typestring–LinkedIn media upload type (default: IMAGE_SHARING).
NameTypeReqDescription
urnstring–urn:li:digitalmediaAsset:… to pass as media_urn

No examples provided.

user_posts ~96

Get recent posts published by a LinkedIn member (via profileUpdatesV2). Paginate with start/count.

NameTypeReqDescription
account_idintegeryesReach id of the LinkedIn account to act on, from list_accounts.
countinteger–Number of posts (max 50).
linkedin_id_or_urlstringyesLinkedIn member ID, vanity name, or profile URL.
startinteger–Pagination offset.
NameTypeReqDescription
postsarray––
total_postsinteger––

No examples provided.

visit_profile ~143

Simulate a profile view, triggering a 'viewed your profile' notification for the target member.

NameTypeReqDescription
account_idintegeryesReach id of the LinkedIn account to act on, from list_accounts.
idempotency_keystring–Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedI…
linkedin_id_or_urlstringyesLinkedIn member ID, vanity name, or profile URL.
NameTypeReqDescription
visitedboolean––

No examples provided.

withdraw_invitation ~146

Withdraw a pending sent connection request.

NameTypeReqDescription
account_idintegeryesReach id of the LinkedIn account to act on, from list_accounts.
idempotency_keystring–Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedI…
linkedin_id_or_urlstringyesThe LinkedIn member: profile URL, vanity name (the part after /in/), Sales Navigator URL, or internal member id.
NameTypeReqDescription
withdrawnboolean––

No examples provided.

Common questions

What is the Reach MCP — LinkedIn for AI agents server?

Reach MCP — LinkedIn for AI agents is listed in the public MCP registry as com.reachmcp/linkedin. LinkedIn for AI agents: inbox, invitations, Sales Navigator search, posts. Quotas and webhooks. This page covers its hosted endpoint (https://app.reachmcp.com/mcp).

Is the Reach MCP — LinkedIn for AI agents server safe to use?

Reach MCP — LinkedIn for AI agents scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Reach MCP — LinkedIn for AI agents server expose?

Reach MCP — LinkedIn for AI agents exposes 52 tools: reach_playbooks, list_accounts, delete_account, get_account_quotas, update_account_quotas, and 47 more. Their descriptions and schemas cost roughly 8,304 tokens of context every time the server is loaded.

Does the Reach MCP — LinkedIn for AI agents server require authentication?

No. We connected to Reach MCP — LinkedIn for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Reach MCP — LinkedIn for AI agents server still maintained?

Reach MCP — LinkedIn for AI agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.