Remote MCP · Endpoint

Cross + Covenant Bible MCP server

No. Cross + Covenant Bible answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://crossandcovenant.co/api/mcp/bible

The last check completed an MCP handshake.

Registry name
co.crossandcovenant/bible
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Public-domain Bible text (WEB and KJV), reading plans and a daily devotional. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Cross + Covenant Bible
CheckedResultHandshake
1 hour agoHandshake completed73 ms
1 day agoHandshake completed74 ms
2 days agoHandshake completed110 ms
3 days agoHandshake completed173 ms
4 days agoHandshake completed73 ms
5 days agoHandshake completed65 ms
6 days agoHandshake completed114 ms
9 days agoHandshake completed298 ms
11 days agoHandshake completed97 ms
14 days agoHandshake completed188 ms
16 days agoHandshake completed54 ms
18 days agoHandshake completed70 ms
20 days agoHandshake completed115 ms
22 days agoHandshake completed53 ms
24 days agoHandshake completed86 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 Cross + Covenant Bible and makes no claim about it beyond what these checks measured.