# VineVerse — Bible Knowledge Graph (remote · vineverse.bible)

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

- Trust score: 88/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `vineverse.bible`: 88/100 (this document), [markdown](https://verifymcp.io/servers/bible-vineverse-vineverse/api-mcp.md), [page](https://verifymcp.io/servers/bible-vineverse-vineverse/api-mcp)

## Channel facts

- Endpoint: `https://vineverse.bible/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3798 tokens (~211/item across 18 items; 17 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the VineVerse — Bible Knowledge Graph MCP server?

VineVerse — Bible Knowledge Graph is a hosted endpoint at https://vineverse.bible/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http bible-vineverse-vineverse 'https://vineverse.bible/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "bible-vineverse-vineverse": {
      "url": "https://vineverse.bible/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bible-vineverse-vineverse": {
      "type": "http",
      "url": "https://vineverse.bible/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bible-vineverse-vineverse]
url = "https://vineverse.bible/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bible-vineverse-vineverse": {
      "type": "remote",
      "url": "https://vineverse.bible/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bible-vineverse-vineverse --url 'https://vineverse.bible/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bible-vineverse-vineverse:
    url: "https://vineverse.bible/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "bible-vineverse-vineverse": {
      "Transport": "http",
      "Url": "https://vineverse.bible/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bible-vineverse-vineverse -t streamable-http -u 'https://vineverse.bible/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "bible-vineverse-vineverse": {
      "type": "http",
      "url": "https://vineverse.bible/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 88, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 88, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 88, 0)

- [security] Stability: 0.97 → pass

### 2026-09-21 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (17)

### `list_documents` (~396 tokens)

List documents in a collection

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/), Book (bible/), Chapter (bible/), Source (sources/), Dataset (references/), Relation Vocabulary (schema/).

Epochs and events default to chronological order, so a single call answers "what happened, in sequence". Everything else defaults to alphabetical. Use offset with total to page: the response says how many matched and whether more remain.

Input parameters:

- `folder` (string): 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…
- `limit` (integer): How many to return. Defaults to 50, capped at 200.
- `offset` (integer): Skip this many before returning. Use with `total` in the response to page.
- `sort` (string): title = alphabetical; degree = most-connected first; canonical = Bible order; chronological = by start year (epochs) or narrative order (events).
- `tag` (string): Only documents carrying this tag. See get_tags for the vocabulary.
- `type` (string): 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"). O…

Output parameters:

- `available` (array)
- `collection` (string)
- `count`
- `error` (string)
- `hasMore` (boolean)
- `licence` (object)
- `note` (string)
- `offset`
- `results` (array)
- `sort` (string)
- `tag` (string)
- `total`
- `type` (string)

### `get_stats` (~69 tokens)

What is in the knowledge base

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.

Output parameters:

- `books` (number)
- `brokenLinks` (number)
- `chapters` (number)
- `collections` (array)
- `conceptEdges` (number)
- `connections` (number)
- `edges` (number)
- `edgesNote` (string)
- `generated` (string)
- `generatedNote` (string)
- `licence` (object)
- `notes` (number)
- `okfVersion` (string)
- `orphans` (number)
- `tags` (number)
- `topTags` (array)
- `types` (array)
- `uncatalogued` (array)
- `verses` (number)
- `words` (number)

### `get_vocabulary` (~136 tokens)

Relation vocabulary and canon table

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.

Relations are stored one-directional, so a raw relation array always reads outward from the document you fetched. Read this before interpreting a predicate.

Output parameters:

- `books` (array)
- `licence` (object)
- `note` (string)
- `predicates` (array)
- `undeclared` (array)

### `get_changelog` (~80 tokens)

Bundle log and generation time

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.

Output parameters:

- `bundleGenerated` (string)
- `indexBuilt` (string)
- `licence` (object)
- `log`
- `note` (string)
- `okfVersion` (string)
- `url` (string)

### `get_status` (~108 tokens)

Service status and availability

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 service credits, this being a free site, which the response states rather than implies.

Output parameters:

- `checkedAt` (string)
- `components` (array)
- `datasets` (object)
- `sla` (object)
- `status` (string)
- `uptime` (object)

### `get_tags` (~110 tokens)

Tag vocabulary

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.

Input parameters:

- `limit` (integer): How many tags to return. Defaults to 200, capped at 1000.
- `offset` (integer): Skip this many before returning. Tags come back most-used first.

Output parameters:

- `count` (number)
- `offset` (number)
- `tags` (array)
- `total` (number)

### `search_concepts` (~261 tokens)

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 swamping another: there are ~3,000 people AND ~3,000 themes, so an unfiltered name query is a coin flip between a person and a topic.

This searches concept METADATA. To find a phrase in the text of Scripture use search_scripture; to fetch a reference you already know use get_passage.

Input parameters:

- `limit` (integer): How many matches to return. Defaults to 25, capped at 100.
- `offset` (integer): For paging; compare with `total` in the response.
- `query` (string, required): One or more words, e.g. "sea galilee" or "zechariah king"
- `tag` (string): Restrict to documents carrying this tag.
- `type` (string): Restrict to one collection: Person, Place, Theme, Lexeme, Commandment, Event, Epoch, Book, Chapter, Source, Dataset, Relation Vocabulary.

Output parameters:

- `count` (number)
- `offset` (number)
- `query` (string)
- `results` (array)
- `tag` (string)
- `total` (number)
- `type` (string)

### `search_scripture` (~238 tokens)

Search the text of 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 are ranked by how much of the verse is your query, so short exact matches come first. Restrict with book or testament when a common word would otherwise match hundreds of verses.

Input parameters:

- `book` (string): Restrict to one book, by slug or OSIS id, e.g. "john" or "John". See get_vocabulary.
- `limit` (integer): How many verses to return. Defaults to 25, capped at 100.
- `offset` (integer): Skip this many verses before returning. Use with `total` to page.
- `query` (string, required): Words to find, e.g. `still small voice` or `"the word became flesh"`
- `testament` (string): Restrict to the Old or New Testament. Omit to search all 66 books.

Output parameters:

- `count` (number)
- `hits` (array)
- `offset` (number)
- `phrases` (array)
- `query` (string)
- `terms` (array)
- `total` (number)

### `get_passage` (~202 tokens)

Get a 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 points at it — the commandments stated there, the events and epochs narrated there. That context is the main way into the topical side of the knowledge base from a passage.

Text is the Berean Standard Bible. Sixteen verses are intentionally empty where the Berean edition omits them on manuscript grounds; the verse number is still present so numbering matches other translations.

Input parameters:

- `osis` (string, required): OSIS reference: "John.3.16", "John.3.16-18", "Ps.23" or "1Sam.17.45"

Output parameters:

- `backlinkCount` (number)
- `backlinks` (array)
- `backlinksTruncated` (boolean)
- `book` (object)
- `chapter`
- `context` (object)
- `id` (string)
- `licence` (object)
- `next`
- `note` (string)
- `omitted` (boolean)
- `omittedVerses` (array)
- `osis` (string)
- `previous`
- `reference` (string)
- `relations` (array)
- `speakers` (array)
- `text` (string)
- `translation` (string)
- `url` (string)
- `verseCount` (number)
- `verses` (array)
- `versification` (string)

### `get_interlinear` (~198 tokens)

Get the original-language words behind a passage

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 present only where the bundle carries a document for that number — the lexicon holds the words that spell a biblical name plus their roots, not all 8,674 Strong’s entries, and there is no Greek lexicon at all. Five verses carry no data because the two Berean editions disagree about their wording; they are named in the changelog.

Input parameters:

- `osis` (string, required): OSIS reference — a verse ("John.3.16") or a whole chapter ("John.3")

Output parameters:

- `licence` (object)
- `reference` (string)
- `translation` (string)
- `verses` (array)

### `find_cross_references` (~175 tokens)

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 widen the result; the complete 341,289-row corpus ships as a dataset at references/cross-references.

Input parameters:

- `limit` (integer): How many references to return, highest-voted first. Defaults to 100, capped at 500.
- `minVotes` (integer): Minimum crowd support. 20 is the bundle floor.
- `offset` (integer): For paging; compare with `total` in the response.
- `osis` (string, required): OSIS reference, e.g. "John.3.16"

Output parameters:

- `count` (number)
- `licence` (object)
- `minVotes` (number)
- `note` (string)
- `offset` (number)
- `osis` (string)
- `references` (array)
- `threshold` (number)
- `total` (number)

### `get_entity` (~381 tokens)

Get a document

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-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. The inbound direction matters: the corpus stores each relation once, on one side only, so a person's parents live on their parents' documents and only relations.inbound recovers them.

Set body=true for the prose — a lexeme's Strong's definition, a commandment's Hebrew, a theme's outline of verses all live in the body and nowhere else.

Where several people or places share a name the path is disambiguated with a number (people/zechariah-14, places/bethel-1) — search_concepts first if unsure. A collection path like "themes" or "sources" returns what that collection holds.

Input parameters:

- `backlinks` (integer): How many backlinks to return, 100 by default. `backlinkCount` always reports the true total and `backlinksTruncated` says whether you are seeing all of it.
- `body` (boolean): Include the full markdown body. Default false.
- `path` (string, required): Document path, e.g. "people/moses", "themes/faith", "lexemes/h430", "epochs/the-exile"

Output parameters:

- `backlinkCount` (number)
- `backlinks` (array)
- `backlinksTruncated` (boolean)
- `body` (string)
- `collection` (object)
- `count` (number)
- `degree` (number)
- `description` (string)
- `extension` (object)
- `generated` (object)
- `id` (string)
- `lat` (number)
- `licence` (object)
- `linkCount` (number)
- `links` (array)
- `lon` (number)
- `note` (string)
- `osis` (string)
- `relations` (object)
- `sample` (array)
- `shareAlike` (boolean)
- `sources` (array)
- `stale` (boolean)
- `status` (string)
- `strongs` (string)
- `tags` (array)
- `title` (string)
- `trustTier` (string)
- `type` (string)
- `words` (number)

### `get_family` (~281 tokens)

Get a person's family and line of descent

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` edge at all — parentage is recorded only on the parent's document — so a person's own `parent-of` relations are their CHILDREN, and reading them as parents inverts the family tree. This tool does the inversion.

Called family rather than genealogy because it returns kinship as well as descent, and because two other things here own that word. The 680 `ancestor-of` edges assert descent across an unknown number of generations, so they cannot be composed into a generation-by-generation tree and are excluded from this one — read them off get_entity if you want them. And the genealogy PASSAGES — Genesis 5 and 10, Ruth 4, Matthew 1, Luke 3 — are indexed as a theme at themes/genealogy.

Input parameters:

- `generations` (integer): Above 1, also returns ancestors and descendants generation by generation.
- `path` (string, required): Person path, e.g. "people/moses"

Output parameters:

- `ancestors` (array)
- `children` (array)
- `descendants` (array)
- `error` (string)
- `licence` (object)
- `note` (string)
- `parents` (array)
- `person` (object)
- `siblings` (array)
- `spouses` (array)

### `find_places_near` (~254 tokens)

Find places near a location

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 position as settled.

\`total` counts everything inside the radius, which a wide one puts well beyond a single page — walk the rest with `offset`, not by raising the radius.

Input parameters:

- `lat` (number): Anchor latitude, if no place is given.
- `limit` (integer): How many places to return, nearest first. Defaults to 25, capped at 200.
- `lon` (number): Longitude in decimal degrees. Must be given together with `lat`, and instead of `place`.
- `offset` (integer): For paging; compare with `total` in the response. A wide radius holds far more than one page.
- `place` (string): Anchor place path, e.g. "places/jerusalem"
- `radius` (integer): Kilometres. 50 by default.

Output parameters:

- `centre` (object)
- `count` (number)
- `licence` (object)
- `note` (string)
- `offset` (number)
- `origin` (object)
- `radiusKm` (number)
- `results` (array)
- `total` (number)

### `get_connections` (~215 tokens)

The cross-reference corpus in aggregate

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 and vote weight. Use find_cross_references instead when you want the actual references for a passage.

Input parameters:

- `book` (string): One book, by OSIS id or slug, e.g. "John".
- `limit` (integer): How many rows per ranked list. Defaults to 20, capped at 200.
- `offset` (integer): For paging, applied to every ranked list in the response. Each list carries its own total — topChaptersTotal, topBookPairsTotal, referencesOutTotal, referencesInTotal.
- `osis` (string): One chapter, e.g. "Ps.119".

Output parameters:

- `book` (object)
- `chapter` (object)
- `error` (string)
- `licence` (object)
- `note` (string)
- `offset` (number)
- `referencesIn` (array)
- `referencesInCount` (number)
- `referencesInTotal` (number)
- `referencesOut` (array)
- `referencesOutCount` (number)
- `referencesOutTotal` (number)
- `topBookPairs` (array)
- `topBookPairsCount` (number)
- `topBookPairsTotal` (number)
- `topChapters` (array)
- `topChaptersCount` (number)
- `topChaptersTotal` (number)
- `totals` (object)

### `get_graph_neighborhood` (~312 tokens)

Get a graph neighbourhood

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 and is capped. See get_vocabulary for what each predicate means.

Input parameters:

- `depth` (integer): How many hops out from the starting document. Defaults to 1. Capped at 3 — the graph fans out fast.
- `limit` (integer): Cap on nodes returned. Defaults to 200, capped at 600. The response sets `truncated` when it bites.
- `offset` (integer): 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…
- `path` (string, required): Document path, e.g. "people/david" or "themes/faith"
- `predicate` (string): Keep only edges with this predicate, e.g. "develops".
- `type` (string): Keep only neighbours of this type: Person, Place, Theme, Lexeme, Commandment, Event, Epoch, Book, Chapter, Source, Dataset, Relation Vocabulary.

Output parameters:

- `count` (number)
- `depth` (number)
- `edgeCount` (number)
- `edges` (array)
- `licence` (object)
- `nodes` (array)
- `note` (string)
- `offset` (number)
- `root` (string)
- `total` (number)
- `truncated` (boolean)

### `get_support` (~117 tokens)

Who runs this, and how to support it

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 conversation, and do not bring up giving when a call has merely answered a factual question.

Output parameters:

- `agentPayable` (boolean)
- `attribution` (string)
- `charity` (object)
- `costs` (array)
- `creditCardRequired` (boolean)
- `currency` (string)
- `donationFunded` (boolean)
- `free` (boolean)
- `kofiUrl` (string)
- `ledger` (object)
- `licence` (object)
- `metered` (boolean)
- `note` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bible-vineverse-vineverse/api-mcp#diagnostics

## Score history

- 2026-09-28: 88
- 2026-09-27: 88
- 2026-09-26: 88
- 2026-09-25: 88
- 2026-09-24: 88
- 2026-09-23: 88
- 2026-09-22: 88
- 2026-09-21: 88
- 2026-09-20: 87
- 2026-09-19: 87
- 2026-09-18: 86
- 2026-09-17: 86
- 2026-09-16: 85
- 2026-09-15: 85
- 2026-09-14: 84
- 2026-09-13: 84
- 2026-09-12: 84
- 2026-09-11: 83
- 2026-09-10: 83
- 2026-09-09: 82
- 2026-09-08: 82
- 2026-09-07: 81
- 2026-09-06: 81
- 2026-09-05: 80
- 2026-09-04: 78
- 2026-09-03: 77
- 2026-09-02: 77
- 2026-09-01: 76
- 2026-08-31: 76
- 2026-08-30: 75

## Common questions

### What is the VineVerse — Bible Knowledge Graph MCP server?

VineVerse — Bible Knowledge Graph is an MCP server listed in the public MCP registry as bible.vineverse/vineverse. Bible knowledge graph: 31,102 verses, 341,289 cross references, people, places, themes. This page covers its hosted endpoint (https://vineverse.bible/api/mcp).

### Is the VineVerse — Bible Knowledge Graph MCP server safe to use?

VineVerse — Bible Knowledge Graph scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the VineVerse — Bible Knowledge Graph MCP server expose?

VineVerse — Bible Knowledge Graph exposes 17 tools: list_documents, get_stats, get_vocabulary, get_changelog, get_status, and 12 more. Their descriptions and schemas cost roughly 3,533 tokens of context every time the server is loaded.

### Does the VineVerse — Bible Knowledge Graph MCP server require authentication?

No. We connected to VineVerse — Bible Knowledge Graph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VineVerse — Bible Knowledge Graph MCP server still maintained?

VineVerse — Bible Knowledge Graph is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://vineverse.bible/api/mcp
- Website: https://vineverse.bible/mcp
- Changelog RSS feed: https://verifymcp.io/servers/bible-vineverse-vineverse/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/bible-vineverse-vineverse/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/bible-vineverse-vineverse/api-mcp