Remote MCP · Endpoint

Lobsters MCP server

No. Lobsters answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/lobsters/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/lobsters
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
146 ms
Tools exposed
45 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Lobsters MCP — stories and discussions from lobste.rs
Listing
From the official MCP registry (active).
Recent checks of Lobsters
CheckedResultHandshake
1 hour agoHandshake completed146 ms
2 days agoHandshake completed57 ms
4 days agoHandshake completed53 ms
5 days agoHandshake completed167 ms
7 days agoHandshake completed53 ms
8 days agoHandshake completed208 ms
9 days agoHandshake completed67 ms
12 days agoHandshake completed44 ms
14 days agoHandshake completed45 ms
15 days agoFailed - the request timed out—
17 days agoHandshake completed64 ms
18 days agoHandshake completed48 ms
19 days agoHandshake completed37 ms
20 days agoHandshake completed34 ms
20 days agoHandshake completed51 ms
22 days agoHandshake completed76 ms
23 days agoHandshake completed47 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 Lobsters and makes no claim about it beyond what these checks measured.