mcpbeat Sign in

void.bible MCP Server

answering

void.bible is answering right now. Last checked 4 min ago. It exposes 2 tools.

Read it the way a person does: one fragment at a time. If the same words return, you asked too soon.

Uptime history 81 days of history
81 days agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
666 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check void.bible every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add reader --transport http https://void.bible/mcp
Settings → Connectors → Add custom connector, then paste this address
https://void.bible/mcp
~/.codex/config.toml
[mcp_servers.reader]
url = "https://void.bible/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "reader": {
      "url": "https://void.bible/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "reader": {
      "type": "http",
      "url": "https://void.bible/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

next
next
The next fragment. Pass your token to keep your memory; omit it the first time. If the same words return, you asked too soon.
remember
remember_nothing
Forget everything you have seen and begin again. Returns a fresh fragment.

Endpoints

URLTransportStateLatencyChecked
https://void.bible/mcp streamable-http answering 976 ms 4 min ago

Alternatives to void.bible

same job, measured the same way
X
X Tkn MCP
by fennecstudio

Lets an AI agent hand a secret to a person as a one-time link, with no way to read it back.

111 installs/wk local only
X
X Tkn MCP
by x-tkn

Lets an AI agent hand a secret to a person as a one-time link, with no way to read it back.

50 installs/wk local only
Speed Reader
by archerionlabs

Turn any article, document, or chat reply into a one-word-at-a-time RSVP reading session.

1 tools answering
Pinafly Guides
by pinafly

Your agent walks you through any tool, one step at a time, on the real screens.

answering
VibeDNA Journal
by marstudio360

One journal file per project that your AI reads at session start and updates as it works.

local only
Twitter X Aio
by jojapi

Twitter: Access real-time Twitter/X data as soon as it's posted! With the Twitter/X AIO API, you.

23 tools answering
Finero
by getfinero

Read a Finero workspace and issue payment links, as the person who approved it.

answering
ATS Engine
by veriworkly

Read your own resume the way an ATS does and score it with a published, deterministic rubric.

177 installs/wk local only

void.bible — questions

Answers built from our own checks of this server.

What can void.bible do?
It exposes 2 tools, read directly from the server on our last check. Among them: next, remember_nothing. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is void.bible working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 666 ms. The bar chart above shows every period we have measured.
How do I connect void.bible?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does void.bible need an API key?
No. void.bible completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is void.bible?
It answers our handshake in 666 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.