Remote MCP · Endpoint

Bible MCP server

No. Bible answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/bible/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/bible
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Bible MCP — wraps the Bible API (free, no auth) https://bible-api.com
Listing
From the official MCP registry (active).
Recent checks of Bible
CheckedResultHandshake
1 hour agoHandshake completed90 ms
1 day agoHandshake completed188 ms
2 days agoHandshake completed84 ms
3 days agoHandshake completed94 ms
4 days agoHandshake completed145 ms
5 days agoHandshake completed148 ms
6 days agoHandshake completed289 ms
9 days agoHandshake completed96 ms
12 days agoHandshake completed67 ms
14 days agoHandshake completed60 ms
16 days agoHandshake completed71 ms
18 days agoHandshake completed60 ms
20 days agoHandshake completed81 ms
23 days agoHandshake completed61 ms
25 days agoHandshake completed52 ms
26 days agoHandshake completed113 ms
28 days agoHandshake completed60 ms
29 days agoHandshake completed217 ms

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

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