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.
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.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
claude mcp add reader --transport http https://void.bible/mcp
https://void.bible/mcp
[mcp_servers.reader]
url = "https://void.bible/mcp"
{
"mcpServers": {
"reader": {
"url": "https://void.bible/mcp"
}
}
}
{
"servers": {
"reader": {
"type": "http",
"url": "https://void.bible/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
next
remember_nothing
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://void.bible/mcp | streamable-http | answering | 976 ms | 4 min ago |
Lets an AI agent hand a secret to a person as a one-time link, with no way to read it back.
Lets an AI agent hand a secret to a person as a one-time link, with no way to read it back.
Turn any article, document, or chat reply into a one-word-at-a-time RSVP reading session.
Your agent walks you through any tool, one step at a time, on the real screens.
One journal file per project that your AI reads at session start and updates as it works.
Twitter: Access real-time Twitter/X data as soon as it's posted! With the Twitter/X AIO API, you.
Read a Finero workspace and issue payment links, as the person who approved it.
Read your own resume the way an ATS does and score it with a published, deterministic rubric.
Answers built from our own checks of this server.