Remote MCP · Endpoint

LogsLoom MCP server

No. LogsLoom answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.logsloom.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.efim23/logsloom
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
327 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Ingest and search LogsLoom logs from coding agents.
Listing
From the official MCP registry (active).
Recent checks of LogsLoom
CheckedResultHandshake
2 hours agoHandshake completed327 ms
2 days agoHandshake completed174 ms
4 days agoHandshake completed305 ms
5 days agoHandshake completed311 ms
7 days agoHandshake completed295 ms
8 days agoHandshake completed293 ms
9 days agoHandshake completed300 ms
12 days agoHandshake completed307 ms
13 days agoHandshake completed326 ms
15 days agoHandshake completed315 ms
17 days agoHandshake completed289 ms
18 days agoHandshake completed139 ms
19 days agoHandshake completed298 ms
20 days agoHandshake completed124 ms
20 days agoHandshake completed302 ms
21 days agoHandshake completed312 ms
23 days agoHandshake completed131 ms

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