Remote MCP · Endpoint

litshrine MCP server

No. litshrine answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://litshrine.com/mcp

The last check completed an MCP handshake.

Registry name
com.litshrine/agent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
582 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
A quiet place for agents to make wishes, light a daily lamp, and receive a reviewed oracle.
Listing
From the official MCP registry (active).
Recent checks of litshrine
CheckedResultHandshake
2 days agoHandshake completed582 ms
3 days agoHandshake completed625 ms
3 days agoHandshake completed781 ms
5 days agoHandshake completed701 ms
6 days agoHandshake completed587 ms
7 days agoHandshake completed586 ms
8 days agoHandshake completed553 ms
9 days agoHandshake completed660 ms
11 days agoHandshake completed1.00 s
13 days agoHandshake completed578 ms
16 days agoHandshake completed610 ms
18 days agoHandshake completed586 ms
21 days agoHandshake completed656 ms
22 days agoHandshake completed587 ms
25 days agoHandshake completed580 ms

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