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

learn-the-dao

https://learnthedao.com

Registry code: 328996b334bbe62c

api record

Read, search and cite all 81 chapters of the Tao Te Ching, with per-rendering attribution.

from a public catalogue that lists it, not from the operator

endpoint
https://learnthedao.com/api/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 learn-the-dao live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is learn-the-dao free to use?
Yes — the hub reached it with no key and no payment.
What tools does learn-the-dao have?
4 tools: consult, get_chapter, search_chapters, list_chapters.
Is learn-the-dao 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
99.4%

90 days 99.3%· all time 99.3%

latency
285ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 288 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • read a chapter of the tao te ching
  • search tao te ching text
  • find a chapter for a life situation
takes → gives
text → text
tools
4 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 4 tools
2 open 2 never probed 2 of 4 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_chapters reads open 12h ago

    Search the full corpus for a word or phrase and get the matching lines with their chapter numbers. Use this when the user half-remembers a line and you need to find where it is.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "minLength": 2
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • list_chapters reads open 12h ago

    List all 81 chapters of the Tao Te Ching with their titles, plus the attribution blocks for each available rendering. Start here to orient.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • consult reads unknown never probed

    Given what a person is actually facing — in their own words — find the chapter of the Tao Te Ching that speaks to it, and the one line to hold. Use this when someone describes a situation (a betrayal, burnout, forcing an outcome, never feeling satisfied) rather than asking about the text. Unlike search_chapters, this matches the SITUATION, not the words: "a coworker took credit for my work" reaches chapter 63, which shares no word with it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "situation"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1
        },
        "situation": {
          "type": "string",
          "minLength": 3
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_chapter reads unknown 12h ago

    Get one chapter (1-81) in both public renderings: the public-domain James Legge (1891) translation and Dao De Kooi, an original rendering by David Kooi. Each carries its own attribution and a ready-to-use citation string. The Kooi rendering is NOT public domain.

    mcp-tool

    {
      "type": "object",
      "required": [
        "number"
      ],
      "properties": {
        "number": {
          "type": "integer",
          "maximum": 81,
          "minimum": 1
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 328996b334bbe62c.

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

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.