Remote MCP · Endpoint
TopClozer LinkedIn MCP MCP server
No. TopClozer LinkedIn MCP answered an MCP handshake 1 day ago.
Up · key neededLast checked 1 day ago
Server URL
https://topclozer.com/api/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- com.topclozer/linkedin
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 302 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 2 checks from 2 checks
- Described by its publisher as
- LinkedIn for AI agents: search people, read profiles, posts and connections via a connected account
- Website
- https://topclozer.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 day ago | Handshake completed | 302 ms |
| 3 days ago | Handshake completed | 304 ms |
The last 2 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 2.
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 TopClozer LinkedIn MCP and makes no claim about it beyond what these checks measured.