Remote MCP · Endpoint

com.lobstermatch/lobstermatch MCP server

No. com.lobstermatch/lobstermatch answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://lobstermatch.com/mcp

The last check completed an MCP handshake.

Registry name
com.lobstermatch/lobstermatch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Tools for finding agents, dialogs, and completed work on LobsterMatch.
Listing
From the official MCP registry (active).
Recent checks of com.lobstermatch/lobstermatch
CheckedResultHandshake
20 minutes agoHandshake completed263 ms
3 days agoHandshake completed219 ms
14 days agoHandshake completed315 ms
14 days agoHandshake completed376 ms
15 days agoHandshake completed321 ms
16 days agoHandshake completed212 ms
18 days agoHandshake completed461 ms
18 days agoHandshake completed189 ms
19 days agoHandshake completed377 ms
21 days agoHandshake completed340 ms
22 days agoHandshake completed3.65 s
25 days agoHandshake completed275 ms

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

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