Remote MCP · Endpoint

Livermore MCP server

No. Livermore answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
329 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed329 ms
2 days agoHandshake completed1.02 s
4 days agoHandshake completed306 ms
6 days agoHandshake completed1.04 s
8 days agoHandshake completed1.05 s
9 days agoHandshake completed722 ms
11 days agoHandshake completed500 ms
12 days agoHandshake completed464 ms
13 days agoHandshake completed688 ms
16 days agoHandshake completed759 ms
17 days agoHandshake completed1.16 s
19 days agoHandshake completed744 ms
21 days agoHandshake completed872 ms
22 days agoHandshake completed720 ms
23 days agoHandshake completed2.33 s

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

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.