Skip to content
Simple Cohort, LLC logo

Simple Cohort, LLC MCP server

Which MCP servers are Simple Cohort, LLC's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to Simple Cohort, LLC

Whose server it is
  • Registry namecom.simplecohortllc.bible/shepherd-bible-apiverified in the MCP registry

The registry name sits under simplecohortllc.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools5
  • Server calls itselfshepherd-bible-api
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 206 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: connect internal systems to ChatGPT or Claude; build custom internal tools for your team; replace repetitive spreadsheet work with automation.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 4 of 5 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-25
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it0 of 3 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer204 ms
  • Space in an agent's context≈ 453 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsB · 87 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 5

What an agent can do with it

  • cannot · connect internal systems to ChatGPT or Claude
  • cannot · build custom internal tools for your team
  • cannot · replace repetitive spreadsheet work with automation

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-25
  • bible_translations

    Return all available Bible translations.

  • bible_books

    Return books and chapter counts for a translation.

  • bible_chapter

    Return all verses, groupings, and red letter data for a chapter.

  • bible_verse

    Return a specific verse, with red letter data if available.

  • bible_search

    Search for verses by keyword or exact match.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "shepherd-bible-api": {
      "type": "http",
      "url": "https://bible.simplecohortllc.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http simplecohortllc https://bible.simplecohortllc.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://bible.simplecohortllc.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.