Remote MCP · Endpoint
io.github.lemmaoracle/mcp MCP server
No. io.github.lemmaoracle/mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.lemma.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.lemmaoracle/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 170 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Verifiable provenance for AI agents — ZK proofs over confidential documents, no plaintext exposure.
- Website
- https://lemma.frame00.com/
- Repository
- https://github.com/lemmaoracle/lemma
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 170 ms |
| 1 day ago | Handshake completed | 238 ms |
| 2 days ago | Handshake completed | 163 ms |
| 3 days ago | Handshake completed | 194 ms |
| 4 days ago | Handshake completed | 166 ms |
| 5 days ago | Handshake completed | 167 ms |
| 6 days ago | Handshake completed | 192 ms |
| 9 days ago | Handshake completed | 168 ms |
| 11 days ago | Handshake completed | 233 ms |
| 14 days ago | Handshake completed | 329 ms |
| 16 days ago | Handshake completed | 276 ms |
| 18 days ago | Handshake completed | 185 ms |
| 20 days ago | Handshake completed | 313 ms |
| 22 days ago | Handshake completed | 252 ms |
| 24 days ago | Handshake completed | 226 ms |
| 26 days ago | Handshake completed | 267 ms |
| 27 days ago | Handshake completed | 189 ms |
| 29 days ago | Handshake completed | 217 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 io.github.lemmaoracle/mcp and makes no claim about it beyond what these checks measured.