Remote MCP · Endpoint

TrulyRandomVerse MCP server

No. TrulyRandomVerse answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://mcp.trulyrandomverse.com/

The last check completed an MCP handshake.

Registry name
com.trulyrandomverse/bible-study
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
214 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Bible study: many editions, Strong's Hebrew and Greek, cross-references, Matthew Henry, the Fathers
Listing
From the official MCP registry (active).
Recent checks of TrulyRandomVerse
CheckedResultHandshake
4 hours agoHandshake completed214 ms
10 days agoHandshake completed109 ms
11 days agoHandshake completed236 ms
11 days agoHandshake completed107 ms
13 days agoHandshake completed148 ms
14 days agoHandshake completed145 ms
15 days agoHandshake completed162 ms
16 days agoHandshake completed128 ms
17 days agoHandshake completed153 ms
19 days agoHandshake completed506 ms
22 days agoHandshake completed162 ms
24 days agoHandshake completed140 ms
26 days agoHandshake completed259 ms
29 days agoHandshake completed148 ms

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