eremos-bible
Registry code: 2e321f344594ddcd
Use these tools when a user wants Thai Bible text. Quote the returned Thai exactly; do not paraphrase it and present the result as Scripture. Name the source as the Eremos Translation and mention it is a draft under review. Verse numbers follow English (BSB) numbering.
- endpoint
- https://mcp.eremosapp.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is eremos-bible live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
- Is eremos-bible free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does eremos-bible have?
- 4 tools: list_books, get_passage, get_translation_notes, search_text.
- Is eremos-bible safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_books unknown never probed
List all 66 books with English and Thai names, USFM codes and chapter counts.
{ "type": "object", "properties": {} }arguments 4 linesget_passage unknown 3h ago
Return the Eremos Translation (Thai) text of a Bible reference, word for word, with verse numbers and a link. Accepts English or Thai book names, abbreviations or USFM codes: 'John 3:16', 'Jn 3:16-18', 'Psalm 23', '1 Cor 13:4-7', 'ยอห์น 3:16', 'JHN 3'. One chapter or a verse range within one chapter.
{ "type": "object", "required": [ "reference" ], "properties": { "reference": { "type": "string", "description": "A Bible reference, e.g. 'John 3:16' or 'สดุดี 23'" } } }arguments 12 linesget_translation_notes unknown 3h ago
Return the published decision record for one verse: the Hebrew or Greek words, the Thai chosen, and the translator's reason, plus any notes. Useful when a user asks why the Thai reads as it does.
{ "type": "object", "required": [ "reference" ], "properties": { "reference": { "type": "string", "description": "A single verse, e.g. 'Mark 1:35'" } } }arguments 12 linessearch_text unknown 3h ago
Find verses in the Eremos Translation whose Thai text contains the given words (all words must appear). Optionally limit to one book. Returns up to `limit` verses with references.
{ "type": "object", "required": [ "query" ], "properties": { "book": { "type": "string", "description": "Optional book name or code to search within" }, "limit": { "type": "integer", "default": 15, "maximum": 50, "minimum": 1 }, "query": { "type": "string", "description": "Thai words or phrase, e.g. 'ความรักมั่นคง'" } } }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id2e321f344594ddcd.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2e321f344594ddcd/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2e321f344594ddcd?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.