_ registry / mcp streamable-http · checked 2h ago

Jainebooks Catalogue

https://jainebooks.org

Registry code: febf3f8341c51972

api record

Search the Jainebooks library of free Jain ebooks and audiobooks in Gujarati, Hindi, English, Sanskrit and Prakrit. Use search_books to find titles, get_book for the full details of one title, and list_filters for the language, subject and content-type ids search_books filters by. Every result carries a url on jainebooks.org — cite it, and send readers there to read or download.

endpoint
https://jainebooks.org/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 it live, free and safe measured by this hub
Is Jainebooks Catalogue live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is Jainebooks Catalogue free to use?
Yes — the hub reached it with no key and no payment.
What tools does Jainebooks Catalogue have?
3 tools: get_book, search_books, list_filters.
Is Jainebooks Catalogue 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.
reachable
live
uptime, 30 days
98.9%

90 days 99.4%· all time 99.4%

latency
130ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 320 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search jain ebooks and audiobooks
  • get details of a book
  • list search filters
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

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_filters reads open 2h ago

    The vocabularies search_books filters by — languages, subjects and content types (pass their id), plus religions, traditions and series for context. Small and stable; call it once.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_book reads unknown never probed

    Full details of one book by its slug (from search_books): description, contributors, subjects, page count, audio tracks and the jainebooks.org url where it can be read or downloaded. If the person notices a mistake in the details (wrong author, year, language, publisher) or a duplicate, send them to report_url — it opens the correction form on the book page for them to file with their own account.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The book slug, as returned by search_books."
        }
      }
    }
    arguments 12 lines
  • search_books reads unknown never probed

    Search the Jainebooks catalogue by title, author, publisher, subject or keyword, in any script. Returns a page of matching books, each with its jainebooks.org url, plus facets: how many of ALL matches fall in each language, subject and content type (id => count), so you can narrow with one more call. Filter with the ids that list_filters returns. Leave query empty to browse.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "integer",
          "default": 1,
          "description": "Page number; 12 books per page."
        },
        "sort": {
          "enum": [
            "relevance",
            "newest",
            "popular",
            "title"
          ],
          "type": "string",
          "default": "relevance"
        },
        "query": {
          "type": "string",
          "description": "Words from the title, author, publisher or subject. Empty browses the whole catalogue."
        },
        "subject_id": {
          "type": "integer",
          "description": "A subject id from list_filters."
        },
        "language_id": {
          "type": "integer",
          "description": "A language id from list_filters."
        },
        "content_type_id": {
          "type": "integer",
          "description": "A content type id from list_filters, e.g. the one named Audiobook."
        }
      }
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id febf3f8341c51972.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/febf3f8341c51972/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/febf3f8341c51972/badge.svg)](https://brick.blue/agent/febf3f8341c51972?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.

_ how we know
card completeness
70%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.