Lab: check this course's own '141 tools' claim

This course has stated that the 1Claw MCP server exposes 141 tools, sourced from 1Claw's own documentation early in this course. It has never been checked against a live, running artifact until now. This lab does that, and the result is not a clean confirmation.

1. 1

   Fetch the public server card. It is what any MCP client discovers before ever connecting.

   code Copy

   curl -s https://1claw.co/.well-known/mcp/server-card.json | python3 -c '
   import json, sys
   d = json.load(sys.stdin)
   print("version:    ", d["version"])
   print("tools_count:", d["tools_count"])
   print("first five: ", d["tools"][:5])
   '

2. 2

   A real number, and it is not 141.

   text Copy

   version:     0.60.0
   tools_count: 30
   first five:  ['list_vaults', 'create_vault', 'list_secrets', 'get_secret', 'put_secret']

Sit with that before reaching for an explanation. The honest position is not 'the course was wrong' and it is not 'the card is wrong' either, because a discrepancy this clean, exactly 30 versus 141, could mean several different things, and this endpoint alone cannot tell you which.

• The most likely explanation is that this well-known card is a curated discovery preview rather than the complete registry. The five tools shown are exactly the ones you would put in front of a client deciding whether to connect: vaults and secrets, the core of the product, not the full surface behind an authenticated stdio session.
• It could also mean the documented number is stale. 1Claw ships fast, at v0.60.0 as of this lab, and a course written against one release can drift from a later one in either direction.
• What it cannot mean is that you should simply pick whichever number is more convenient. The correct next step is the one you cannot take from here: connect over authenticated stdio, as the MCP lesson two lessons ago described, and call the tool-listing method yourself.