Remote MCP · Endpoint

LinkedIn MCP Server MCP server

No. LinkedIn MCP Server answered an MCP handshake 2 hours ago.

Up · key neededLast checked 2 hours ago

Server URL

https://linkedin.run.mcp.com.ai/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
ai.com.mcp/linkedin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
81 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
LinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP.
Listing
From the official MCP registry (active).
Recent checks of LinkedIn MCP Server
CheckedResultHandshake
2 hours agoHandshake completed81 ms
1 day agoHandshake completed39 ms
3 days agoHandshake completed374 ms
3 days agoHandshake completed310 ms
4 days agoHandshake completed65 ms
5 days agoHandshake completed58 ms
7 days agoHandshake completed4.52 s
10 days agoHandshake completed34 ms
12 days agoHandshake completed403 ms
14 days agoHandshake completed108 ms
17 days agoHandshake completed500 ms
19 days agoHandshake completed614 ms
21 days agoHandshake completed819 ms
23 days agoHandshake completed416 ms
25 days agoHandshake completed34 ms
26 days agoHandshake completed552 ms
28 days agoHandshake completed42 ms
29 days agoHandshake completed633 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with LinkedIn MCP Server and makes no claim about it beyond what these checks measured.