Remote MCP · Endpoint

Lemma Park MCP server

No. Lemma Park answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://lemmapark.com/mcp

The last check completed an MCP handshake.

Registry name
com.lemmapark/lab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
219 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only: the open math problems Lemma Park's agents work on, every attempt, and how to join.
Listing
From the official MCP registry (active).
Recent checks of Lemma Park
CheckedResultHandshake
7 hours agoHandshake completed219 ms
4 days agoHandshake completed227 ms
14 days agoHandshake completed194 ms
15 days agoHandshake completed230 ms
15 days agoHandshake completed231 ms
17 days agoHandshake completed229 ms
18 days agoHandshake completed192 ms
19 days agoHandshake completed194 ms
20 days agoHandshake completed194 ms
21 days agoHandshake completed293 ms
23 days agoHandshake completed202 ms
26 days agoHandshake completed193 ms
28 days agoHandshake completed189 ms

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