Overview
A Bible verse and scripture API. Bible works by querying a large database of bible verses to retrieve the verse based on the book, chapter, and verse provided. It returns the bible verse in a structured format.
Live Test Verified Bible Verse Data for AI Agents Source →
The tool
Once your client is connected to the VerveContext server, this appears in its tool list as VerifiedBibleVerseDataforAIAgents. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.
{
"name": "VerifiedBibleVerseDataforAIAgents",
"arguments": {
"book": "Genesis",
"version": "KJV",
"chapter": "5"
}
}You do not name the tool yourself; the model picks it. Asking about Genesis in the terms this source covers is enough for it to reach for VerifiedBibleVerseDataforAIAgents on its own — naming it explicitly also works, and is the way to force the call.
Connecting
One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp"
}
}
}https://api.vervecontext.com/v1/mcpPer-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.
| Argument | Type | Description |
|---|---|---|
bookRequired | string | The name of the book in the bible (e.g., Genesis) |
versionRequired | string | The Bible translation versionKJVASVBBEDarby |
chapterRequired | integer | The chapter number in the book range 1–∞ |
verseOptional | integer | The verse number in the chapter range 1–∞ |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"text": "But with thee will I establish my covenant; and thou shalt come into the ark, thou, and thy sons, and thy wife, and thy sons' wives with thee.",
"book": "Genesis",
"abbr": "gn",
"chapter": 6,
"verses": [
18
],
"version": "KJV",
"testament": "Old Testament",
"bookNumber": 1,
"totalChapters": 50,
"totalVersesInChapter": 22,
"wordCount": 29
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
text | string | But with thee will I establish my covenant; and thou shalt come into the ark, thou, and thy sons, and thy wife, and thy sons' wives with thee. | The complete text of the requested verse or passage |
book | string | Genesis | Full name of the biblical book (e.g., Genesis, Matthew) |
abbr | string | gn | Two-letter abbreviation of the book name |
chapter | number | 6 | Chapter number of the requested verse |
verses | array | [18] | Array of verse numbers included in the response |
version | string | KJV | Bible translation version (e.g., KJV, NIV, ESV) |
testament | string | Old Testament | Old Testament or New Testament classification |
bookNumber | number | 1 | Position of the book in the Bible (1-66) |
totalChapters | number | 50 | Total number of chapters in this book |
totalVersesInChapter | number | 22 | Total number of verses in the current chapter |
wordCount | number | 29 | Number of words in the returned verse(s) |
Why ground on it
A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.
Point an evaluation at text: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.
Failure modes
Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This source is not part of VerveContext. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Daily Devotional Notifications
- Devotional mobile apps schedule daily morning push notifications that display a random verse along with its book and chapter reference.
- Worship Slide Generation
- To prepare church projection slides, presentation software queries chapter text and verse numbers to format reading prompts automatically.
- Multitranslation Scripture Study
- Academic study platforms pull the same verse across Darby, ASV, and KJV versions so researchers can compare wording line by line.
- Custom Journal Publishing
- When laying out printable prayer planners, publishing tools inject verse text and testament classifications into daily reading header blocks.
Other ways to use Verified Bible Verse Data for AI Agents
Set up Verified Bible Verse Data for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.
Related
More in Data Lookup: