Remote MCP · Endpoint
void.bible MCP server
No. void.bible answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://void.bible/mcp
The last check completed an MCP handshake.
- Registry name
- bible.void/reader
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 131 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Read it the way a person does: one fragment at a time. If the same words return, you asked too soon.
- Website
- https://void.bible/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 131 ms |
| 2 days ago | Handshake completed | 105 ms |
| 4 days ago | Handshake completed | 167 ms |
| 5 days ago | Handshake completed | 145 ms |
| 7 days ago | Handshake completed | 137 ms |
| 8 days ago | Handshake completed | 1.81 s |
| 9 days ago | Handshake completed | 149 ms |
| 12 days ago | Handshake completed | 166 ms |
| 13 days ago | Handshake completed | 158 ms |
| 15 days ago | Handshake completed | 743 ms |
| 16 days ago | Handshake completed | 62 ms |
| 17 days ago | Handshake completed | 137 ms |
| 19 days ago | Handshake completed | 61 ms |
| 19 days ago | Handshake completed | 236 ms |
| 20 days ago | Handshake completed | 91 ms |
| 21 days ago | Handshake completed | 112 ms |
| 22 days ago | Handshake completed | 72 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 void.bible and makes no claim about it beyond what these checks measured.