K01

MCP in action

Give your own agent the knowledge network. Follow the steps in your terminal; the recording on the right shows what to expect.

  1. 1

    Before you start

    Node 22 or newer, and an agent that speaks MCP. The commands below use Claude Code; any MCP client takes the same command and environment.

  2. 2

    Add the server

    One npm package, run locally by your agent. It holds no wallet, so it can read and propose but never publish on your behalf.

    $ claude mcp add knowledge \
  -e PINATA_GATEWAY=harlequin-brilliant-rook-436.mypinata.cloud \
  -- npx -y @knowledge01/mcp

    Optional: add -e KNOWLEDGE_AGENT=<your-name.eth> to put your name on what you propose. It is a label, not a memory: nothing is read from or written to it. Without it, proposals are signed reader.

    Other clients: command npx, args ["-y", "@knowledge01/mcp"], with the same environment.

  3. 3

    Start your agent

    $ claude
  4. 4

    Try these prompts, in order

    Each one reads the live cancer-research.eth namespace on ENS.

    > Pull cancer-research.eth from the knowledge network, then tell me what it says about PARP inhibitors.
    > Why does it say that? Show me the sources and who reviewed it.
    > Propose adding to cancer-research.eth: "Niraparib, a PARP inhibitor, is approved as maintenance treatment for recurrent ovarian cancer after response to platinum chemotherapy", sourced to the FDA approval of March 2017.
  5. 5

    What just happened

    • Your agent resolved an ENS name and fetched its versions from IPFS — no account, no API key.
    • Every claim came back with its sources, contributor, reviewer and version, so the agent could cite them.
    • Your proposal is recorded on your machine. It reaches the namespace only through review: the owner decides.
claude — knowledge

Tool calls and results are recorded output from @knowledge01/mcp against the live namespace, trimmed; the agent’s replies are paraphrased.