Reach MCP — LinkedIn for AI agents
REMOTE · APP.REACHMCP.COM
LinkedIn for AI agents: inbox, invitations, Sales Navigator search, posts, jobs, quotas, webhooks.
Available components
Last scanned (3 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.53 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Sept 26 0
First indexed and scored.
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 5 Nov 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 | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7f9d51ea6a397ccb0ec39de1ae283007 |
| 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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://app.reachmcp.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://app.reachmcp.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://app.reachmcp.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://app.reachmcp.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://app.reachmcp.com/mcp |
| Authorisation server | https://mcp-reach-backend-3icgkfijmq-ew.a.run.app |
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 | Auth required | 401 | |
| http (plaintext) | http://app.reachmcp.com/mcp | HTTPS enforced | 301 | https://app.reachmcp.com/mcp |
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 →
update_account_quotas ~354
Update one or more quota configuration fields for a LinkedIn account. Only provided fields are updated.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | yes | Reach id of the LinkedIn account to act on, from list_accounts. |
| daily_comments_conf | integer | – | Daily limit for 'comments' on this account; 0 means unlimited. |
| daily_imports_recruiter_conf | integer | – | Daily limit for 'imports_recruiter' on this account; 0 means unlimited. |
| daily_imports_salesnav_conf | integer | – | Daily limit for 'imports_salesnav' on this account; 0 means unlimited. |
| daily_imports_standard_conf | integer | – | Daily limit for 'imports_standard' on this account; 0 means unlimited. |
| daily_invitations_conf | integer | – | Daily limit for 'invitations' on this account; 0 means unlimited. |
| daily_messages_conf | integer | – | Daily limit for 'messages' on this account; 0 means unlimited. |
| daily_posts_conf | integer | – | Daily limit for 'posts' on this account; 0 means unlimited. |
| daily_reactions_conf | integer | – | Daily limit for 'reactions' on this account; 0 means unlimited. |
| daily_visits_conf | integer | – | Daily limit for 'visits' on this account; 0 means unlimited. |
| idempotency_key | string | – | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | – | – |
| quotas | object | – | – |
| updated | boolean | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | yes | Reach id of the LinkedIn account to act on, from list_accounts. |
| idempotency_key | string | – | 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_urn | string | yes | URN of the scheduled post (urn:li:…), from list_scheduled_posts. |
| scheduled_at | integer | – | Unix timestamp in milliseconds. |
| text | string | – | Plain text to send or post. |
| Name | Type | Req | Description |
|---|---|---|---|
| post_urn | string | – | – |
| updated | boolean | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_ids | array | – | Only these LinkedIn account ids; omit for every account of the user. |
| description | string | – | Free-text label for your own reference. |
| endpoint_id | integer | yes | Webhook endpoint id, from list_webhook_endpoints. |
| events | array | – | Event types to subscribe to (message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached) or ['*']. |
| idempotency_key | string | – | 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_active | boolean | – | Pause (false) or resume (true) deliveries. |
| url | string | – | https URL that receives the signed JSON POST (http accepted for localhost only). |
| Name | Type | Req | Description |
|---|---|---|---|
| account_ids | array|null | – | – |
| consecutive_failures | integer | – | – |
| created_at | string | – | – |
| description | string | – | – |
| disabled_reason | string | – | – |
| events | array | – | – |
| id | integer | – | – |
| is_active | boolean | – | – |
| last_delivery_at | string | – | – |
| url | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | yes | Reach id of the LinkedIn account to act on, from list_accounts. |
| idempotency_key | string | – | 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_url | string | yes | Publicly accessible URL of the image to upload. |
| media_upload_type | string | – | LinkedIn media upload type (default: IMAGE_SHARING). |
| Name | Type | Req | Description |
|---|---|---|---|
| urn | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | yes | Reach id of the LinkedIn account to act on, from list_accounts. |
| count | integer | – | Number of posts (max 50). |
| linkedin_id_or_url | string | yes | LinkedIn member ID, vanity name, or profile URL. |
| start | integer | – | Pagination offset. |
| Name | Type | Req | Description |
|---|---|---|---|
| posts | array | – | – |
| total_posts | integer | – | – |
No examples provided.
visit_profile ~143
Simulate a profile view, triggering a 'viewed your profile' notification for the target member.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | yes | Reach id of the LinkedIn account to act on, from list_accounts. |
| idempotency_key | string | – | 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_url | string | yes | LinkedIn member ID, vanity name, or profile URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| visited | boolean | – | – |
No examples provided.
withdraw_invitation ~146
Withdraw a pending sent connection request.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | integer | yes | Reach id of the LinkedIn account to act on, from list_accounts. |
| idempotency_key | string | – | 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_url | string | yes | The LinkedIn member: profile URL, vanity name (the part after /in/), Sales Navigator URL, or internal member id. |
| Name | Type | Req | Description |
|---|---|---|---|
| withdrawn | boolean | – | – |
No examples provided.
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
claude mcp add --transport http com-reachmcp-linkedin 'https://app.reachmcp.com/mcp'
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, jobs, quotas, 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 36 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?
Yes. Reach MCP — LinkedIn for AI agents asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.