Remote MCP · Endpoint

Socketlist MCP server

No. Socketlist answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://socketlist.pages.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.thunderbid/socketlist-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search a directory of 800+ open-source MCP servers: find, compare and get install configs.
Listing
From the official MCP registry (active).
Recent checks of Socketlist
CheckedResultHandshake
1 hour agoHandshake completed111 ms
19 hours agoHandshake completed92 ms
2 days agoHandshake completed91 ms
3 days agoHandshake completed100 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed71 ms
6 days agoHandshake completed146 ms
8 days agoHandshake completed97 ms
10 days agoHandshake completed63 ms
13 days agoHandshake completed94 ms
15 days agoHandshake completed63 ms
17 days agoHandshake completed92 ms
19 days agoHandshake completed87 ms
21 days agoHandshake completed68 ms

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

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 Socketlist and makes no claim about it beyond what these checks measured.