HumanMCP — Kapoost
Attach a personal humanMCP endpoint so your agent can assert proof of authorship and manage license posture for work you publish.
Overview
humanMCP is an MCP server for the Build phase that provides proof of authorship and license control for individual human creators via a hosted remote endpoint.
What is this MCP server?
- Personal MCP server positioned for human creators, not generic org bots
- Proof-of-authorship and license-control capabilities via remote https://kapoost.humanmcp.net/mcp
- Streamable HTTP MCP transport (version 0.3.0) for cloud-hosted access without local stdio
- Pairs with humanMCP marketplace federation for listing human-verified offers
- GitHub implementation at kapoost/humanmcp-go for self-host or fork paths
- Published server version 0.3.0 with streamable-http remote URL kapoost.humanmcp.net/mcp
- Repository source github.com/kapoost/humanmcp-go
- Server title humanMCP — kapoost per MCP registry metadata
What problem does it solve?
Indie creators struggle to prove ownership and enforce licenses when AI agents remix, republish, or broker their work across tools.
Who is it for?
Solo creators publishing IP who want a personal MCP identity layer without running complex auth infrastructure.
Skip if: Builders who only need anonymous open-source snippets with no attribution or licensing requirements.
What do I get? / Deliverables
After connecting the streamable-http remote, your agent can consult humanMCP for authorship and license signals before offering or trading creative output.
- Connected personal humanMCP remote with authorship and license tools available to the agent
- Documented license posture agents can query before distribution actions
- Foundation identity endpoint for federated marketplace listings
Recommended MCP Servers
Journey fit
Creators integrate identity and licensing controls while building offerings; the same server supports launch and operate when you enforce terms on distributed artifacts. Integrations is the shelf because you wire a remote streamable-http MCP identity surface into your agent stack rather than shipping a standalone app feature first.
How it compares
Creator identity and license MCP endpoint, not a federated search catalog (see humanMCP Marketplace).
Common Questions / FAQ
Who is humanMCP for?
Human creators and solo founders who publish attributable work and want MCP-aware agents to respect authorship and license rules.
When should I use humanMCP?
Use it when integrating agent workflows that list, sell, or collaborate on your creations and you need provable human authorship plus license control.
How do I add humanMCP to my agent?
Add a remote MCP server with type streamable-http and URL https://kapoost.humanmcp.net/mcp in your Claude Code, Cursor, or compatible client, then verify tools in a dry-run session.