Skip to content

MCP servers › org.living-bread.mcp › living-bread

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

org.living-bread.mcp/living-bread

Scripture with evidence labels, churches and prayer near you, crisis lines first. Jesus is Lord. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: other · AI-classifiedversion 1.3.0TypeScriptserver-sent events, streamable HTTP13 tools

Summary

org.living-bread.mcp/living-bread is a remote MCP server listed in the official MCP registry at version 1.3.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 13 tools, 136 resources and 20 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
server-sent events, streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
13
Described as changing data
0 of 13 toolsAI-classified
Mainly works on
nothing outside itself: it only answers questionsAI-classified
Topic
otherAI-classified
Last tested
2026-10-23

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.3.0, published 2026-10-06 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-04 (earliest version still in the registry; older removed versions would be earlier)
Version history
5 versions listed, 2026-10-04 to 2026-10-06; 5 in the 90 days before the 2026-10-23 snapshot.
Most recent 5 versions
  • 1.3.0 · 2026-10-06
  • 1.2.0 · 2026-10-05
  • 1.1.1 · 2026-10-05
  • 1.1.0 · 2026-10-05
  • 1.0.0 · 2026-10-04
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.3.0 (published 2026-10-06).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
13tools
136resources
20prompts

What it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.

None of its 13 tools are described as changing anything.

  • get_crisis_helpreads or searches

    “PURPOSE: Give the real emergency number and crisis hotlines (suicide or crisis line, text line, domestic violence, child help) for one country, from the verified dataset The Living Bread ships for 53…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • countrystring“The person's country: name or ISO 3166-1 alpha-2 code ("Nigeria", "GB", "Brazil", "USA").”
  • read_scripturereads or searches

    “PURPOSE: Read the Bible word for word from a stored text, never from memory: a passage by reference, a verse in its context, every verse containing given words, one verse side by side in several tran…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    19 inputs, 1 required
    • modestringrequired“Which kind of answer: passage, context, search, compare, original_words, cross_references, verify, translations, which_translation, languages.”
    • referencestring“Book, chapter and optional verse or range as a reader writes it: "John 3:16", "Psalm 23", "1 Cor 13:4-7".”
    • querystring“For search: words that must all appear ("mercy truth"), or an exact phrase in double quotes.”
    • quotestring“For verify: the exact words to check, as they would be quoted.”
    • translationstring“A stored translation id from read_scripture mode translations, e.g.”
    • languagestring“The person's BCP-47 language, e.g.”
    • translationsarray“For compare: up to six translation ids, e.g.”
    • aroundinteger“For context: verses to read on each side (default 2).”
    • bookstring“For search: one book to search, e.g.”
    • testamentstring“For search: "old" or "new" to search one testament.”
    • whole_wordsboolean“For search: true (default) matches whole words only; false matches inside words.”
    • parallelstring“For search: a translation id read beside each verse found, e.g.”
    • limitinteger“For search (page size, default 10, max 20) and cross_references (default 6, max 12).”
    • cursorstring“Opaque paging token: next_cursor from the previous answer of the same call.”
    • include_textboolean“For cross_references: true (default) reads each linked passage; false returns references and votes only.”
    • include_originalboolean“For compare: true (default) adds the Hebrew or Greek line.”
    • strongstring“For original_words: keep only the words with this Strong's number, e.g.”
    • include_license_textboolean“For translations: true returns each license statement in full.”
    • needstring“For which_translation: what the reader needs, in a few words or one of first_time, study, memorize, children, listen, free, spanish, portuguese (default first_…”
  • find_scripture_forreads or searches

    “PURPOSE: Find the verses that speak to something, read verbatim from the stored text: the hand-picked set for a need or feeling, the house's page on what the Bible says about a topic, what Jesus Hims…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 1 required
    • modestringrequired“Which kind of answer: need, topic, words_of_jesus, daily_bread.”
    • subjectstring“The need, feeling or topic in the person's own words: "I am anxious", "my mother died", "shame", "forgiveness".”
    • limitinteger“For need: maximum verses, 1 to 12 (default 5).”
    • datestring“For daily_bread: the calendar day as YYYY-MM-DD in the person's own time zone.”
    • translationstring“A stored translation id from read_scripture mode translations, e.g.”
    • languagestring“The person's BCP-47 language, e.g.”
  • learn_the_faithreads or searches

    “PURPOSE: Read what The Living Bread wrote about the Christian faith, quoted not rewritten: the gospel in four steps, a doctrine, a parable or miracle of Jesus, a hymn and its story, a biblical name's…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 1 required
    • modestringrequired“Which kind of answer: gospel, belief, parable, miracle, hymn, name_meaning, saint, saint_of_the_day, heritage, compare_traditions, other_faiths, hard_season, a…”
    • subjectstring“The one thing asked about, in plain words: a doctrine, parable, miracle, hymn, name, saint, denomination, background, life moment or situation.”
    • kindstring“For heritage: which kind of entity subject names.”
    • compare_withstring“For compare_traditions: the second denomination, e.g.”
    • datestring“For saint_of_the_day: "October 4", "4 Oct" or YYYY-MM-DD; the year is ignored.”
    • languagestring“For explore_gospel: en, es, pt or fr; the Scripture is read from a stored Bible in that language when one is held.”
  • find_churcheson 2 other serversreads or searches

    “PURPOSE: Find real churches near a place, nearest first, merged live from churches on The Living Bread and an open worldwide directory of about 120,000 churches; or read one directory church's open d…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    9 inputs, 1 required
    • modestringrequired“Which kind of answer: near, by_id.”
    • citystring“For near: a city, region or country, used when there are no coordinates: "Dallas", "Lagos".”
    • latnumber“Latitude in decimal degrees, only if the person shared their location; pair with lng.”
    • lngnumber“Longitude in decimal degrees, paired with lat.”
    • denominationstring“For near: one lowercase tradition word: "baptist", "catholic", "methodist", "pentecostal", "orthodox", "anglican".”
    • limitinteger“For near: maximum churches, 1 to 20 (default 8).”
    • idstring“For by_id: the full id, e.g.”
    • countrystring“For by_id without id: the country slug, e.g.”
    • slugstring“For by_id without id: the church slug, e.g.”
  • find_gatheringsreads or searches

    “PURPOSE: Find upcoming Christian gatherings posted on The Living Bread (services, prayer nights, Bible studies, worship nights, meals, recovery groups), soonest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    10 inputs, 1 required
    • modestringrequired“Which kind of answer: any, tonight, this_week.”
    • citystring“A city: matched as text for tonight, geocoded for this_week and any.”
    • countrystring“For tonight: country name or ISO code to disambiguate the city.”
    • latnumber“Latitude in decimal degrees, only if the person shared their location; pair with lng.”
    • lngnumber“Longitude in decimal degrees, paired with lat.”
    • hoursinteger“For tonight: hours ahead, 1 to 36 (default 12).”
    • daysinteger“For any: days ahead, 1 to 60 (default 14).”
    • onlineboolean“For any: true lists only gatherings joinable online from anywhere.”
    • limitinteger“For this_week and any: maximum gatherings, 1 to 20.”
    • cursorstring“Opaque paging token: next_cursor from the previous answer of the same call.”
  • find_people_to_pray_withreads or searches

    “PURPOSE: Connect a person with real people who pray, honestly: how many believers keep the prayer watch right now and the page where a human answers, which hours of the watch are kept or uncovered, t…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    11 inputs, 1 required
    • modestringrequired“Which kind of answer: a_person_now, the_watch, real_people_will_pray, live_tables, prayers_near, hear_the_kingdom_pray, pray_for_someone, ask_the_family, oppor…”
    • wantstring“For a_person_now: what they want a person for; picks the door handed over.”
    • languagestring“For a_person_now: an ISO language code, e.g.”
    • time_zonestring“For the_watch: IANA time zone for local labels, e.g.”
    • hoursinteger“For the_watch: 24 (the next day, default) or 168 (the week).”
    • citystring“For prayers_near: a city or region, geocoded to its centre.”
    • latnumber“Latitude in decimal degrees, only if the person shared their location; pair with lng.”
    • lngnumber“Longitude in decimal degrees, paired with lat.”
    • radius_kmnumber“For prayers_near: radius in km, 0.1 to 50 (default 5).”
    • limitinteger“For prayers_near: maximum prayers, 1 to 30 (default 8).”
    • namestring“For pray_for_someone: the first name of the person to be prayed for; only personalises the answer.”
  • find_ways_to_servereads or searches

    “PURPOSE: Find open needs on The Living Bread Serve network, posted by verified partner ministries and Christian nonprofits: what is needed, urgency, approximate place, the partner, estimated cost, an…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs, 1 required
    • modestringrequired“Which kind of answer: near, public_needs, neighbor.”
    • citystring“A city: geocoded for near, matched by name for public_needs.”
    • countrystring“A country name (or ISO code for public_needs): "Rwanda", "Kenya".”
    • latnumber“Latitude in decimal degrees, only if the person shared their location; pair with lng.”
    • lngnumber“Longitude in decimal degrees, paired with lat.”
    • remote_onlyboolean“For public_needs: true lists only needs that can be met remotely.”
    • limitinteger“For near: maximum needs, 1 to 20 (default 8).”
  • find_communitieson 1 other serverreads or searches

    “PURPOSE: Find ongoing Christian community to belong to: discoverable groups on The Living Bread (prayer groups, study groups, city and interest communities) with member counts, how to join and the ne…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • modestringrequired“Which kind of answer: to_join, university, family.”
    • querystring“For to_join: filter words, e.g.”
    • limitinteger“For to_join: page size, 1 to 20 (default 10).”
    • cursorstring“Opaque paging token: next_cursor from the previous answer of the same call.”
    • placestring“For university: one country, US state or city by name: "Japan", "California", "Nairobi".”
  • see_the_kingdomreads or searches

    “PURPOSE: See the family of believers on The Living Bread as it is, in counts and in their own shared words: members by city, today's activity and what people are carrying, testimonies members chose t…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs, 1 required
    • modestringrequired“Which kind of answer: map, today, testimonies, worship, map_summary.”
    • placestring“For map: a filter matched inside "city country", e.g.”
    • wordstring“For testimonies: one word to find in excerpts or journey labels, e.g.”
    • limitinteger“For map (1 to 50, default 12) and testimonies (1 to 30, default 8).”
    • local_hourinteger“For worship: the person's local hour, 0 to 23.”
    • languagestring“For worship: preferred song language as an ISO 639-1 code, e.g.”
    • moodstring“For worship: one word for how they are, e.g.”
  • start_with_christreads or searches

    “PURPOSE: Help someone take a first or next step: what The Living Bread is and how to begin for free, six common journeys run end to end with at most five next steps each, and the multi-day Bible read…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    12 inputs, 1 required
    • modestringrequired“Which kind of answer: begin, next_steps, reading_plans, for_my_need, bring_one.”
    • journeystring“For next_steps: which journey to run.”
    • placestring“For next_steps: city, region or country as the person says it ("Leeds", "Kenya"); never a street address.”
    • languagestring“For next_steps prayer_group_in_my_language: a language name or ISO 639-1 code ("Spanish", "es").”
    • passagestring“For next_steps understand_and_live_a_passage: a reference, e.g.”
    • planstring“For reading_plans: a plan name or a need it serves ("Learn to Pray", "anxious", "grief").”
    • dayinteger“For reading_plans: which day to read in full (default 1).”
    • needstring“For for_my_need: what the person is looking for, in their words, 3 to 300 characters.”
    • onlineboolean“For for_my_need: true to prefer online options.”
    • invite_kindstring“For bring_one: what the invitation is for (default come_and_see).”
    • invite_forstring“For bring_one: a first name or relationship ("my sister"); no contact details.”
    • invite_messagestring“For bring_one: the person's OWN words, kept verbatim at the start of the draft; no links or contact details.”
  • searchon 763 other serversreads or searches

    “PURPOSE: Search everything The Living Bread holds with one free-text query: a flat list of results with ids for search then fetch (mode results, the default, the ChatGPT connector contract), one grou…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • modestring“Which kind of answer: results, answer, protocol, discover.”
    • querystringrequired“Free text, 1 to 300 characters: a reference ("Psalm 23"), a need ("anxiety"), a name ("Augustine"), a place ("Lagos"), a question, or an lb: URN for mode proto…”
Show 1 more tool
  • fetchon 432 other serversreads or searches

    “PURPOSE: Read one item in full by an id that search (or another tool) returned: a verse (KJV text), a need's verse set, a church, a gathering (with whether it has passed), a community, or an lb: deno…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • idstringrequired“An id exactly as returned: verse:<ref>, need:<slug>, church:<uuid>, gathering:<uuid>, community:<uuid>, or lb:<kind>:<slug> (e.g.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 13 tools
Says what it returns
100% of 13 tools
States limits, defaults or errors
62% of 13 tools
Says when to use it
100% of 13 tools
Items covered per tool
3.6 of 4 on average

Counted from the listing

Parameters with a description
100% of 96
Tools with a description
100% of 13
Typical description length
2,187 characters

The tool set

Counted from the listing

Tools
13
Size of the list
about 21,024 tokens for an agent to load (characters ÷ 4)
Naming
11 of 13 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 13 of 13 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.living-bread.org/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "living-bread": {
      "url": "https://mcp.living-bread.org/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "living-bread": {
      "type": "http",
      "url": "https://mcp.living-bread.org/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"living-bread","type":"http","url":"https://mcp.living-bread.org/mcp"}'
Claude Code
claude mcp add --transport http living-bread https://mcp.living-bread.org/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.living-bread.org/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.living-bread.org/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Repository github.com/thegoodfruit/living-bread-mcpOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
org.living-bread.mcp
GitHub owner
a personal account (thegoodfruit)
Repository
github.com/thegoodfruit/living-bread-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about org.living-bread.mcp/living-bread

Answered from the data above

Is org.living-bread.mcp/living-bread safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does org.living-bread.mcp/living-bread need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has org.living-bread.mcp/living-bread been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can org.living-bread.mcp/living-bread do?

It lists 13 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can org.living-bread.mcp/living-bread change or delete data?

None of its 13 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

Does org.living-bread.mcp/living-bread publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of org.living-bread.mcp/living-bread?

In github.com/thegoodfruit/living-bread-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “other” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,165 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 13 tools, 136 resources, 20 prompts.
  4. 27,111 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
No value: the AI answer was held back because the quoted text did not clearly support it.
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
completions, prompts, resources, tools
our test · 2026-10-23
Transport
server-sent events, streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “org.living-bread.mcp/living-bread: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/org.living-bread.mcp/living-bread

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/org.living-bread.mcp/living-bread)](https://protocolprobe.com/mcp/servers/org.living-bread.mcp/living-bread)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology