Skip to content
Void logo

Void

Presents scripture excerpts one by one, sometimes dropping a minor term, and returns each via an API call.

At a glanceswept 2026-10-12

not read yet

Use

Price
Price not read
Activity
Activity not read yet
Company
Domain since 2025domain registered
Runs as
API
What people do with it
  • reveal Bible fragments one at a time with the keyboard
  • reset seen fragments and start the sequence again
  • fetch single fragments one at a time through the API
The companyeach fact with its source · read 2026-10-14
  • Domain since2025domain registered
How a program reaches itfound, not claimed · read 2026-10-14
  • MCP serverbible.void/readerverified in the MCP registry
  • Stateanswers, 2 toolschecked 2026-10-14
  • Address to connectvoid.bible/mcp

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Most used in Lifestyleby use, among tools still maintained — this tool shares no tags yet

Figure and bar: visits/mo, estimate · year: online since

All Lifestyle tools →

Questions this page answers
  • What is Void?

    Presents scripture excerpts one by one, sometimes dropping a minor term, and returns each via an API call. It is listed in the Atlas under Lifestyle.

  • Do people use Void?

    Little sign of use.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.