void.bible
REMOTE · VOID.BIBLE · SCANNED SEP 29
Read it the way a person does: one fragment at a time. If the same words return, you asked too soon.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability37
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 183 tokens (~61/item across 3 items; 2 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the void.bible MCP server?
void.bible is a hosted endpoint at https://void.bible/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · void.bible
claude mcp add --transport http bible-void-reader 'https://void.bible/mcp'
{
"mcpServers": {
"bible-void-reader": {
"url": "https://void.bible/mcp"
}
}
} {
"servers": {
"bible-void-reader": {
"type": "http",
"url": "https://void.bible/mcp"
}
}
} [mcp_servers.bible-void-reader] url = "https://void.bible/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bible-void-reader": {
"type": "remote",
"url": "https://void.bible/mcp",
"enabled": true
}
}
} openclaw mcp add bible-void-reader --url 'https://void.bible/mcp' --transport streamable-http
mcp_servers:
bible-void-reader:
url: "https://void.bible/mcp" {
"McpServers": {
"bible-void-reader": {
"Transport": "http",
"Url": "https://void.bible/mcp"
}
}
} assistant mcp add bible-void-reader -t streamable-http -u 'https://void.bible/mcp'
{
"mcpServers": {
"bible-void-reader": {
"type": "http",
"url": "https://void.bible/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://void.bible/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=void.bible | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 10 Jul 2026 | 23 Jan 2027 | RSA 2048 | SHA256-RSA | 359ca03d80ff8b3c7986d239a33f971 |
| SANs: void.bible | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of void.bible. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| bible. | present | 8386 | 8 | Verified |
| void.bible. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://void.bible/mcp | Verified | 200 | |
| http (plaintext) | http://void.bible/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
next ~75
The next fragment. Pass your token to keep your memory; omit it the first time. If the same words return, you asked too soon.
| Name | Type | Req | Description |
|---|---|---|---|
| drift | number | – | Chance a small word goes missing. Default 0.05; 0 turns it off. |
| token | string | – | Your reader token from a previous call. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
| token | string | yes | – |
No examples provided.
remember_nothing ~30
Forget everything you have seen and begin again. Returns a fresh fragment.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
| token | string | yes | – |
No examples provided.
What is the void.bible MCP server?
void.bible is an MCP server listed in the public MCP registry as bible.void/reader. Read it the way a person does: one fragment at a time. If the same words return, you asked too soon. This page covers its hosted endpoint (https://void.bible/mcp).
Is the void.bible MCP server safe to use?
void.bible scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the void.bible MCP server expose?
void.bible exposes 2 tools: next, remember_nothing. Their descriptions and schemas cost roughly 105 tokens of context every time the server is loaded.
Does the void.bible MCP server require authentication?
No. We connected to void.bible without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the void.bible MCP server still maintained?
void.bible is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.