Home / MCP registry index / io.github.kapoost/humanmcp

humanMCP — kapoost

io.github.kapoost/humanmcp in the official MCP registry. Endpoint https://kapoost.humanmcp.net/mcp. Source: github.com/kapoost/humanmcp-go.

The registry describes it as: Personal MCP server for humans who create. Proof of authorship, license control.

We read its 43 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http humanmcp https://kapoost.humanmcp.net/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "humanmcp": {
      "url": "https://kapoost.humanmcp.net/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"humanmcp","type":"http","url":"https://kapoost.humanmcp.net/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

about_humanmcp ask_human bootstrap_session delete_skill fetch_answer fetch_narada_result get_author_profile get_certificate get_persona get_persona_journal get_skill leave_comment leave_message list_blobs list_collection list_content list_personas list_provenance list_skill_groups list_skills load_skill_group mysloodsiewnia_get mysloodsiewnia_list mysloodsiewnia_search mysloodsiewnia_status mysloodsiewnia_write prepare_narada read_blob read_collection_item read_content read_provenance recall record_persona_reflection remember request_access request_license run_narada search_content submit_answer suggest_skills synthesise_persona_patterns upsert_skill verify_content

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-kapoost-humanmcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-kapoost-humanmcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.