Remote MCP · Endpoint

Livermore MCP server

No. Livermore answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://livermore.club/mcp

The last check completed an MCP handshake.

Registry name
io.github.AAAZZZR/livermore
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
343 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
US insider trades, 13F, 13D/G, Form 144, politician trades, financials, shorts; Taiwan stocks. Free.
Listing
From the official MCP registry (active).
Recent checks of Livermore
CheckedResultHandshake
5 hours agoHandshake completed343 ms
9 days agoHandshake completed350 ms
10 days agoHandshake completed339 ms
11 days agoHandshake completed304 ms
12 days agoHandshake completed310 ms
14 days agoHandshake completed1.97 s
14 days agoHandshake completed769 ms
15 days agoHandshake completed348 ms
17 days agoHandshake completed602 ms
19 days agoHandshake completed348 ms
21 days agoHandshake completed311 ms
24 days agoHandshake completed306 ms
26 days agoHandshake completed329 ms
28 days agoHandshake completed1.02 s

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

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