get_author_profileLABSCO SUMMARY
Content served with proof of authorship and terms attached.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Paste a URL — add the endpoint to your client
USE CASES
01
Reading an author's work the way it was meant to be read
Browse the catalogue by type or tag, then read a piece — each item's gate is applied on the way through.
02
Checking that a piece is really theirs
Verify the Ed25519 signature and pull the certificate with its hash, originality index and licence.
03
Licensing something before you use it
Declare the intended use, get the terms back, and have the request logged for audit.
04
Getting past a locked piece
Ask what the gate wants, then submit the challenge answer to unlock it.
05
Asking the human a question
Send the question, get an ID back, and check later whether it has been answered.
06
Finding the relevant piece in a large body of work
Search the full text rather than paging through the whole catalogue.
37 tools
Listed in project docs. Your client may show a different list.
list_contentread_contentsearch_contentrequest_accesssubmit_answerlist_blobsread_blobverify_contentget_certificateupgrade_timestamprequest_licenseleave_commentleave_messageask_humanget_answerbootstrap_sessionrecallrememberquery_vaultlist_vaultlist_skillsget_skillupsert_skilldelete_skilllist_personasget_personaupsert_personadelete_personalist_listingsread_listingrespond_to_listingsubscribe_listingsunsubscribe_listingslist_peersannounce_peerabout_humanmcpBEFORE YOU INSTALL
What to know first
Tools you get
37 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
The documented client connects to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://kapoost.humanmcp.net/mcpMCP Clients
Any MCP client — HTTP
ANY MCP CLIENT — HTTP · JSON
{
"mcpServers": {
"kapoost": {
"type": "http",
"url": "https://kapoost.humanmcp.net/mcp"
}
}
}
