Remote MCP · Endpoint

io.github.ldshaf/daily-scripture-mcp MCP server

No. io.github.ldshaf/daily-scripture-mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://hxoqbbfgkrbzumjczeef.supabase.co/functions/v1/mcp-daily-scripture

The last check completed an MCP handshake.

Registry name
io.github.ldshaf/daily-scripture-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
383 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Daily Bible verse and reflection for morning briefs. Conservative evangelical perspective. ESV.
Listing
From the official MCP registry (active).
Recent checks of io.github.ldshaf/daily-scripture-mcp
CheckedResultHandshake
1 hour agoHandshake completed383 ms
2 days agoHandshake completed287 ms
4 days agoHandshake completed254 ms
5 days agoHandshake completed342 ms
7 days agoHandshake completed363 ms
8 days agoHandshake completed297 ms
9 days agoHandshake completed453 ms
12 days agoHandshake completed289 ms
13 days agoHandshake completed436 ms
15 days agoHandshake completed339 ms
16 days agoHandshake completed473 ms
18 days agoHandshake completed283 ms
19 days agoHandshake completed357 ms
20 days agoHandshake completed334 ms
20 days agoHandshake completed325 ms
21 days agoHandshake completed420 ms
22 days agoHandshake completed567 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 io.github.ldshaf/daily-scripture-mcp and makes no claim about it beyond what these checks measured.