Remote MCP · Endpoint
LinkedIn MCP Server MCP server
No. LinkedIn MCP Server answered an MCP handshake 10 hours ago.
Up · key neededLast checked 10 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
- 819 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- LinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP.
- Website
- https://run.mcp.com.ai/
- Repository
- https://github.com/la-rebelion/hapimcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 10 hours ago | Handshake completed | 819 ms |
| 2 days ago | Handshake completed | 416 ms |
| 4 days ago | Handshake completed | 34 ms |
| 5 days ago | Handshake completed | 552 ms |
| 7 days ago | Handshake completed | 42 ms |
| 8 days ago | Handshake completed | 633 ms |
| 9 days ago | Handshake completed | 50 ms |
| 12 days ago | Handshake completed | 431 ms |
| 13 days ago | Handshake completed | 495 ms |
| 15 days ago | Handshake completed | 719 ms |
| 16 days ago | Handshake completed | 33 ms |
| 17 days ago | Handshake completed | 31 ms |
| 18 days ago | Handshake completed | 38 ms |
| 19 days ago | Handshake completed | 35 ms |
| 20 days ago | Handshake completed | 73 ms |
| 21 days ago | Handshake completed | 30 ms |
| 23 days ago | Handshake completed | 677 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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.