LinkedIn MCP Server
REMOTE · LINKEDIN.RUN.MCP.COM.AI · SCANNED AUG 20
LinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 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.
How do I install the LinkedIn MCP Server server?
LinkedIn MCP Server is a hosted endpoint at https://linkedin.run.mcp.com.ai/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 · linkedin.run.mcp.com.ai
claude mcp add --transport http ai-com-mcp-linkedin 'https://linkedin.run.mcp.com.ai/mcp'
{
"mcpServers": {
"ai-com-mcp-linkedin": {
"url": "https://linkedin.run.mcp.com.ai/mcp"
}
}
} {
"servers": {
"ai-com-mcp-linkedin": {
"type": "http",
"url": "https://linkedin.run.mcp.com.ai/mcp"
}
}
} [mcp_servers.ai-com-mcp-linkedin] url = "https://linkedin.run.mcp.com.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-com-mcp-linkedin": {
"type": "remote",
"url": "https://linkedin.run.mcp.com.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-com-mcp-linkedin --url 'https://linkedin.run.mcp.com.ai/mcp' --transport streamable-http
mcp_servers:
ai-com-mcp-linkedin:
url: "https://linkedin.run.mcp.com.ai/mcp" {
"McpServers": {
"ai-com-mcp-linkedin": {
"Transport": "http",
"Url": "https://linkedin.run.mcp.com.ai/mcp"
}
}
} assistant mcp add ai-com-mcp-linkedin -t streamable-http -u 'https://linkedin.run.mcp.com.ai/mcp'
{
"mcpServers": {
"ai-com-mcp-linkedin": {
"type": "http",
"url": "https://linkedin.run.mcp.com.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 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
- 10 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 6 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 Aug 2026 · Probed https://linkedin.run.mcp.com.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.com.ai | CN=WE1,O=Google Trust Services,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 524af76dd4f363e0e15377f47dd9434 |
| SANs: mcp.com.ai, linkedin.run.mcp.com.ai | ||||||
| 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 linkedin.run.mcp.com.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| com.ai. | absent | Delegated | ||
| mcp.com.ai. | 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://linkedin.run.mcp.com.ai/mcp | Verified | 200 | |
| http (plaintext) | http://linkedin.run.mcp.com.ai/mcp | HTTPS enforced | 301 | https://linkedin.run.mcp.com.ai/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 →
createSharePost Share on LinkedIn, create a share post ~45
Share on LinkedIn, create a share post - Create a new share post on LinkedIn using text, URLs, and images
| Name | Type | Req | Description |
|---|---|---|---|
| createSharePostBody | object | yes | – |
No output schema declared.
No examples provided.
getPersonProfile Get person profile ~21
Get person profile - Get basic profile information for a person
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getSharePosts Get share posts ~44
Get share posts - Retrieve share posts for the authenticated user or organization
| Name | Type | Req | Description |
|---|---|---|---|
| authors | string | – | – |
| count | integer | – | – |
| start | integer | – | – |
No output schema declared.
No examples provided.
What is the LinkedIn MCP Server server?
LinkedIn MCP Server is listed in the public MCP registry as ai.com.mcp/linkedin. LinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP. This page covers its hosted endpoint (https://linkedin.run.mcp.com.ai/mcp).
Is the LinkedIn MCP Server server safe to use?
LinkedIn MCP Server scores 0 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 LinkedIn MCP Server server expose?
LinkedIn MCP Server exposes 3 tools: createSharePost, getSharePosts, getPersonProfile. Their descriptions and schemas cost roughly 110 tokens of context every time the server is loaded.
Does the LinkedIn MCP Server server require authentication?
No. We connected to LinkedIn MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LinkedIn MCP Server server still maintained?
LinkedIn MCP Server has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 6 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.