Analytics
vineverse.bible
Provides browsing and statistical insights into a knowledge base, including document listings, collection statistics, vocabulary, changelog, and tags.
ENDPOINT 1
https://vineverse.bible/api/mcp
MCP server metadata
- Name
- vineverse
- Version
- 1.3.0
VineVerse exposes the Bible as a knowledge graph, built from public-domain Scripture and openly licensed scholarship. WHAT IS IN IT. All 31,102 verses across 1,189 chapters and 66 books; ~3,000 people; ~1,300 places with coordinates; ~3,000 topical themes from Nave's Topical Bible; ~2,900 Strong's Hebrew lexemes; the 613 commandments; ~450 narrative events; ~165 dated epochs on Ussher's chronology; and the typed connections between all of them. Call get_stats for exact counts and the full catalogue. HOW TO USE IT. To find out what exists, use list_documents or get_stats — every collection can be paged through. To find something by name, use search_concepts with a `type` filter. To find a phrase in Scripture, use search_scripture. To read a passage with the people, places and themes it touches, use get_passage. THINGS TO RESPECT. Cross references carry no relationship type — the corpus records that two passages are connected, not why — so do not present a connection as a claim the data does not make. Typed relations are stored one-directional: `parent-of` on a person names their CHILDREN, and get_family exists because reading it as parents inverts the tree. And the data is CC BY 4.0 — events under sa/ are CC BY-SA 4.0, which is viral — so if you surface it to a user, the attribution at https://vineverse.bible/attribution comes with it.
Known tools 15
get_statsThe catalogue: every collection with its document count, its folder, an example path and what it contains, plus graph totals, the most common tags and the licences the data is available under.
Inferred read-onlyget_vocabularyThe closed set of predicates every typed edge in the graph is drawn from — what `develops`, `narrated-in`, `involves`, `stated-in` and `named-by` mean, what their inverses are, which types they connect, and how many edges use each.
Inferred read-onlyget_changelogThe knowledge base's own log file, plus when the data was actually ingested.
Inferred read-onlyget_tagsEvery tag in the bundle with the number of documents carrying it, most common first.
Inferred read-onlysearch_conceptsSearch every document in the knowledge base by name, description, tag, path and type — people, places, themes, lexemes, commandments, events, epochs, books, chapters, sources and datasets alike.
Inferred read-onlysearch_scriptureFull-text search across all 31,102 verses of the Berean Standard Bible.
Inferred read-onlyget_interlinearThe Hebrew, Aramaic or Greek behind the English, word by word, for one verse or a whole chapter.
Inferred read-onlyfind_cross_referencesCross references for a verse or chapter, ordered by crowd support.
Inferred read-onlyget_entityFetch any document in the knowledge base by path: People — people/moses Places — places/bethel-1 Themes — themes/faith Lexemes — lexemes/h430 Commandments — commandments/001-know-there-is-a-g-d Events — sa/events/exodus-from-egypt Epochs — epochs/david-reigns-in-jerusalem Books — bible/john Chapters — bible/john/3 Sources — sources/bibledata Datasets — references/cross-references Schema — schema/relations Returns the document's structured fields, its typed relations in BOTH directions, what links to it, and optionally its full text.
Inferred read-onlyget_familyParents, children, siblings and spouses for any person, and with `generations` above 1 the line of descent — ancestors and descendants gathered one generation at a time.
Inferred read-onlyfind_places_nearBiblical places within a radius, nearest first, with the distance in kilometres.
Inferred read-onlyget_connectionsQuestions about the SHAPE of the cross-reference corpus rather than about one verse: which chapters are the hubs, which books lean on which, how much referencing crosses between the testaments.
Inferred read-onlyget_graph_neighborhoodEverything within N hops of a document, WITH the edges that connect them and the predicate on each.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vineverse]
url = "https://vineverse.bible/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vineverse": {
"type": "http",
"url": "https://vineverse.bible/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vineverse
Remote MCP URL: https://vineverse.bible/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vineverse": {
"url": "https://vineverse.bible/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vineverse": {
"type": "http",
"url": "https://vineverse.bible/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vineverse",
"transport": "streamable-http",
"url": "https://vineverse.bible/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.