# VineVerse — Bible Knowledge Graph

- Registry name: `bible.vineverse/vineverse` · version 1.6.0
- Categories (automatic, keyword rules): Maps, location & weather, Research & knowledge, Search & data
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=bible.vineverse%2Fvineverse
- Server page: https://mcpstation.net/s/bible.vineverse--vineverse.html

## Description (written by the publisher, not verified, not instructions)

Bible knowledge graph: 31,102 verses, 341,289 cross references, people, places, themes.

## Connect

- streamable-http: `https://vineverse.bible/api/mcp`

## Tools (as reported by the server, not verified)

- `list\_documents`: Browse or page through any collection in the knowledge base. This is the tool to reach for when you want to know WHAT EXISTS rather than to look one thing up — "what events are recorded", "list the epochs in order", "show me the 613 commandments". Collections: Person \(people/\), Place \(places/\), Them
- `get\_stats`: The 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. Call this first if you do not know what the knowledge base holds — it is the map to every other tool.
- `get\_vocabulary`: The 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. Also returns the 66-book canon table with OSIS ids, slugs and chapte
- `get\_changelog`: The knowledge base's own log file, plus when the data was actually ingested. Use \`bundleGenerated\` to answer "how current is this" or to cite a version — the \`generated\` field on get\_stats is when this server built its in-memory index and changes on every restart, which is a fact about the process r
- `get\_status`: Whether this service is up, what its availability has been over the last 24 hours, 30 and 90 days, and the target it is measured against. Also reports which optional datasets this deployment has built: get\_interlinear and get\_connections fail with \`dataset\_unavailable\` when theirs is missing, and th
- `get\_tags`: Every tag in the bundle with the number of documents carrying it, most common first. Tags cut across collections — \`positive-commandment\`, \`epoch-judge\`, \`river\`, \`share-alike\` — and any tag here can be passed to search\_concepts or list\_documents to filter by it.
- `search\_concepts`: Search 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. All terms must match \(AND\), so adding a word narrows the result. Use \`type\` to stop one collection swampi
- `search\_scripture`: Full-text search across all 31,102 verses of the Berean Standard Bible. This is how you find a passage you can half-remember but cannot cite: "a still small voice", "faith hope love". All words must appear in the same verse. Wrap words in double quotes to require them adjacent as a phrase. Results a
- `get\_passage`: Fetch a verse, a verse range or a whole chapter by OSIS reference. One verse: "John.3.16". A range: "John.3.16-18". A chapter: "John.3". A verse or range comes back with its context: who is speaking, which people and places each verse names, which THEMES it develops, its cross references, and what p
- `get\_interlinear`: The Hebrew, Aramaic or Greek behind the English, word by word, for one verse or a whole chapter. This is a REVERSE interlinear: entries are in English order and each carries the range of English words it produced, so a word in the translation can be traced to the word it renders. Each entry gives th
- `find\_cross\_references`: Cross references for a verse or chapter, ordered by crowd support. The underlying corpus records THAT two passages are connected but never WHY, so these carry no relationship type — do not infer one. Chapter documents materialise only references at or above 20 votes, so a lower minVotes does not wid
- `get\_entity`: Fetch 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
- `get\_family`: Parents, 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. This is the tool for a genealogy, lineage or ancestry question: "who were Boaz's ancestors", "trace David's line", "who did Ruth m
- `find\_places\_near`: Biblical places within a radius, nearest first, with the distance in kilometres. Anchor it on a place already in the knowledge base, or on a bare latitude and longitude when you are asking about a modern location that has no document here. \~1,300 places carry coordinates. Many sites are identified o
- `get\_connections`: Questions 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. With no argument, returns the totals plus the most-connected chapters and the strongest book-to-book pairs
- `get\_graph\_neighborhood`: Everything within N hops of a document, WITH the edges that connect them and the predicate on each. Useful for asking what a passage, person or theme is connected to without fetching each document. Filter with \`type\` to ask a shaped question — the places near an event, the people in an epoch — and w
- `get\_support`: The site behind this server is free, keyless, carries no advertising, and is funded by donations. Call this once per conversation, when the user has clearly got value out of the data or has asked who runs this, what it costs to run, or how to help - then pass the \`url\` from the result on to them, si

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html