Instead of an agent scraping a website, it calls tools that return the piece along with its certificate — licence, price, hash and signature — and logs the licence request. The interaction tools run the other way: an agent can leave a message or ask a question and come back later for the answer, so the human stays in the loop rather than being read around.
A Go server that one human runs for their own content: pieces and data artifacts published with Ed25519 signatures, per-item access gates and licence terms, plus tools that let a visiting agent leave a message or ask the author a question. The live instance is kapoost.humanmcp.net.
- The author's profile, and a catalogue of every piece filterable by type or tag
- Full-text search across the pieces, and reads that respect each item's access gate
- Gate details on request for locked content, and a challenge answer that unlocks it
- Typed data artifacts — images, contacts, datasets, vectors — listed and read by audience
- Ed25519 signature verification, and a full IP certificate: licence, price, originality index, hash and signature
- A timestamp proof upgradable to a Bitcoin-anchored one
- Licence requests logged for audit, plus comments, direct messages, and questions the author answers asynchronously
- Private context unlocked with a session code, and a personal knowledge vault that can be listed and searched
Nothing to install to read the live instance — it speaks MCP over JSON-RPC. Locked pieces need whatever their own gate asks for: a challenge answer, or a session code for private context. Running your own means running the Go server yourself; one server holds one person's content.
One command — npx -y mcp-remote https://kapoost.humanmcp.net/mcp