_ registry / mcp streamable-http · checked 11m ago

listofbooks

https://www.listofbooks.net

Registry code: 06d84942d04a3858

api record

Look up book series reading orders from ListOfBooks. Each answer is short and links to the full page on listofbooks.net. Calling a tool needs a free ListOfBooks API key, sent as "Authorization: Bearer <key>". Get one at https://www.listofbooks.net/developers. Limits apply per member; when a tool returns a limit error, stop calling until the reset time it gives and send the user the link instead.

endpoint
https://www.listofbooks.net/api/public/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 listofbooks live?
Yes — it answered the hub's last check (checked 11m ago). It answered 100% of checks over the last 30 days.
Is listofbooks free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does listofbooks have?
5 tools: search_authors, find_series_for_book, get_author_series, search_series, get_reading_order.
Is listofbooks 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
100%

90 days 100%· all time 100%

latency
273ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
5 auth-required 5 of 5 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.

  • search_authors auth-required 11m ago

    Find authors by name. Returns up to 5 matches, each linking to the author page.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 3,
      "description": "3 to 200 characters, with at least 3 letters or digits."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • find_series_for_book auth-required never probed

    Given a book's title and author, return the series it belongs to, its position, and the series order.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "title",
    "author"
  ],
  "properties": {
    "title": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "1 to 200 characters, with at least one letter or digit."
    },
    "author": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "1 to 200 characters, with at least one letter or digit."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • get_author_series auth-required 11m ago

    Given an author name, return the best-matching author and the titles of the book series they wrote (up to 25). Use get_reading_order with a title for its books.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "author"
  ],
  "properties": {
    "author": {
      "type": "string",
      "maxLength": 200,
      "minLength": 3,
      "description": "3 to 200 characters, with at least 3 letters or digits."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • search_series auth-required 11m ago

    Find book series by name. Returns up to 5 matches, each linking to its reading-order page.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 3,
      "description": "3 to 200 characters, with at least 3 letters or digits."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • get_reading_order auth-required never probed

    Get the reading order of one book series, looked up by series name. Returns the best match only.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "series"
  ],
  "properties": {
    "series": {
      "type": "string",
      "maxLength": 200,
      "minLength": 3,
      "description": "3 to 200 characters, with at least 3 letters or digits."
    }
  },
  "additionalProperties": false
}
    arguments 16 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 06d84942d04a3858.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/06d84942d04a3858/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/06d84942d04a3858/badge.svg)](https://brick.blue/agent/06d84942d04a3858?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
90%

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.