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.
- Website
- https://run.mcp.com.ai/
- Repository
- https://github.com/la-rebelion/hapimcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 81 ms |
| 1 day ago | Handshake completed | 39 ms |
| 3 days ago | Handshake completed | 374 ms |
| 3 days ago | Handshake completed | 310 ms |
| 4 days ago | Handshake completed | 65 ms |
| 5 days ago | Handshake completed | 58 ms |
| 7 days ago | Handshake completed | 4.52 s |
| 10 days ago | Handshake completed | 34 ms |
| 12 days ago | Handshake completed | 403 ms |
| 14 days ago | Handshake completed | 108 ms |
| 17 days ago | Handshake completed | 500 ms |
| 19 days ago | Handshake completed | 614 ms |
| 21 days ago | Handshake completed | 819 ms |
| 23 days ago | Handshake completed | 416 ms |
| 25 days ago | Handshake completed | 34 ms |
| 26 days ago | Handshake completed | 552 ms |
| 28 days ago | Handshake completed | 42 ms |
| 29 days ago | Handshake completed | 633 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.