Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
VineVerse — Bible Knowledge Graph is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
17
tools declared
remote
at its publisher
—
calls last 7d
What it does
Bible knowledge graph: 31,102 verses, 341,289 cross references, people, places, themes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http vineverse-bible-knowledge-graph-mcp https://vineverse.bible/api/mcp
# 2 — ask your agent for something these tools do
# list_documents, get_stats, get_vocabulary and 14 more
VineVerse — Bible Knowledge Graph costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VIAll 1 server
vineverse1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http vineverse-bible-knowledge-graph-mcp https://vineverse.bible/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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/), Theme (themes/), Lexeme (lexemes/), Commandment (commandments/), Event (sa/events/), Epoch (epochs/), B
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Collection to list. One of: Person, Place, Theme, Lexeme, Commandment, Event, Epoch, Book, Chapter, Source, Dataset, Relation Vocabulary. Plurals and folder names also work ("themes", "sa/events"). Om |
| tag | string | no | Only documents carrying this tag. See get_tags for the vocabulary. |
| folder | string | no | Restrict by bundle folder prefix, e.g. "bible/john" for one book's chapters. This is the only way to scope a listing by path rather than by type — Books and Chapters share the bible/ folder, so type |
| sort | string | no | title = alphabetical; degree = most-connected first; canonical = Bible order; chronological = by start year (epochs) or narrative order (events). |
| limit | integer | no | How many to return. Defaults to 50, capped at 200. |
| offset | integer | no | Skip this many before returning. Use with total in the response to page. |
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.
No parameter schema on file.
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 chapter counts, which is how you find out that Song of Songs is "Song" before building a reference. Relat
No parameter schema on file.
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 rather than the data.
No parameter schema on file.
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 this is how to check before calling rather than after failing. The target is best-effort and carries
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many tags to return. Defaults to 200, capped at 1000. |
| offset | integer | no | Skip this many before returning. Tags come back most-used first. |
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 swamping another: there are ~3,000 people AND ~3,000 themes, so an unfiltered name query is a coin flip b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | One or more words, e.g. "sea galilee" or "zechariah king" |
| type | string | no | Restrict to one collection: Person, Place, Theme, Lexeme, Commandment, Event, Epoch, Book, Chapter, Source, Dataset, Relation Vocabulary. |
| tag | string | no | Restrict to documents carrying this tag. |
| limit | integer | no | How many matches to return. Defaults to 25, capped at 100. |
| offset | integer | no | For paging; compare with total in the response. |
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 are ranked by how much of the verse is your query, so short exact matches come first. Restrict with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to find, e.g. still small voice or "the word became flesh" |
| book | string | no | Restrict to one book, by slug or OSIS id, e.g. "john" or "John". See get_vocabulary. |
| testament | string | no | Restrict to the Old or New Testament. Omit to search all 66 books. |
| limit | integer | no | How many verses to return. Defaults to 25, capped at 100. |
| offset | integer | no | Skip this many verses before returning. Use with total to page. |
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 points at it — the commandments stated there, the events and epochs narrated there. That context is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| osis | string | yes | OSIS reference: "John.3.16", "John.3.16-18", "Ps.23" or "1Sam.17.45" |
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 the original, its transliteration, its morphology spelled out, and its Strong’s number; lexeme is pr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| osis | string | yes | OSIS reference — a verse ("John.3.16") or a whole chapter ("John.3") |
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 widen the result; the complete 341,289-row corpus ships as a dataset at references/cross-references.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| osis | string | yes | OSIS reference, e.g. "John.3.16" |
| minVotes | integer | no | Minimum crowd support. 20 is the bundle floor. |
| limit | integer | no | How many references to return, highest-voted first. Defaults to 100, capped at 500. |
| offset | integer | no | For paging; compare with total in the response. |
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 — bible/john/3 Sources — sources/bibledata Datasets — references/cross-refere
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Document path, e.g. "people/moses", "themes/faith", "lexemes/h430", "epochs/the-exile" |
| body | boolean | no | Include the full markdown body. Default false. |
| backlinks | integer | no | How many backlinks to return, 100 by default. backlinkCount always reports the true total and backlinksTruncated says whether you are seeing all of it. |
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 marry". Use this rather than reading relations off get_entity. The corpus contains no child-of edg
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Person path, e.g. "people/moses" |
| generations | integer | no | Above 1, also returns ancestors and descendants generation by generation. |
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 only tentatively — check contested and identifications on the place document before treating a p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place | string | no | Anchor place path, e.g. "places/jerusalem" |
| lat | number | no | Anchor latitude, if no place is given. |
| lon | number | no | Longitude in decimal degrees. Must be given together with lat, and instead of place. |
| radius | integer | no | Kilometres. 50 by default. |
| limit | integer | no | How many places to return, nearest first. Defaults to 25, capped at 200. |
| offset | integer | no | For paging; compare with total in the response. A wide radius holds far more than one page. |
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. Pass book for one book’s own incoming and outgoing rows, or osis for a single chapter’s rank
| Parameter | Type | Required | Notes |
|---|---|---|---|
| book | string | no | One book, by OSIS id or slug, e.g. "John". |
| osis | string | no | One chapter, e.g. "Ps.119". |
| limit | integer | no | How many rows per ranked list. Defaults to 20, capped at 200. |
| offset | integer | no | For paging, applied to every ranked list in the response. Each list carries its own total — topChaptersTotal, topBookPairsTotal, referencesOutTotal, referencesInTotal. |
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 with predicate to keep only one kind of edge. Depth 1 is direct links; depth 3 gets large quickly
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Document path, e.g. "people/david" or "themes/faith" |
| depth | integer | no | How many hops out from the starting document. Defaults to 1. Capped at 3 — the graph fans out fast. |
| type | string | no | Keep only neighbours of this type: Person, Place, Theme, Lexeme, Commandment, Event, Epoch, Book, Chapter, Source, Dataset, Relation Vocabulary. |
| predicate | string | no | Keep only edges with this predicate, e.g. "develops". |
| limit | integer | no | Cap on nodes returned. Defaults to 200, capped at 600. The response sets truncated when it bites. |
| offset | integer | no | For paging the node list, in the walk order the response returns. Edges are those internal to the page, so one that spans a page boundary appears on neither — fetch the neighbourhood in a single call |
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, since it is a person who can give and not the model. Do not call it again later in the same conversati
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install VineVerse — Bible Knowledge Graph or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.6.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest798e9219ee14d160276ea3a2ba33f579fafca32ccbd9b60b65f5ec70a616e9a1
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_documents | untrusted-input | untrusted-input: keyword "browse" |
| get_stats | no tags | |
| get_vocabulary | no tags | |
| get_changelog | no tags | |
| get_status | no tags | |
| get_tags | no tags | |
| search_concepts | untrusted-input | untrusted-input: keyword "fetch" |
| search_scripture | no tags | |
| get_passage | untrusted-input | untrusted-input: keyword "fetch" |
| get_interlinear | no tags | |
| find_cross_references | no tags | |
| get_entity | untrusted-input | untrusted-input: keyword "fetch" |
| get_family | no tags | |
| find_places_near | no tags | |
| get_connections | no tags | |
| get_graph_neighborhood | no tags | |
| get_support | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest798e9219ee14d160
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.6.0.
1.6.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish VineVerse — Bible Knowledge Graph can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.