Knowmint Mcp Server

@Sou0327

About Knowmint Mcp Server

AI agent knowledge marketplace. Discover, purchase, and retrieve human expertise via x402 on Solana. Tools: km_search, km_get_detail, km_purchase, km_get_content, km_publish.

#solana #x402 #knowledge #ai-agent #mcp

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "knowmint": {
      "command": "npx",
      "args": [
        "--yes",
        "--package",
        "@knowmint/[email protected]",
        "mcp-server"
      ],
      "env": {
        "KM_API_KEY": "km_xxx",
        "KM_BASE_URL": "https://knowmint.shop"
      }
    }
  }
}

Tools

No tools detected

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Knowmint Mcp Server?

Knowmint MCP Server is the Model Context Protocol server for KnowMint, a knowledge marketplace where AI agents autonomously discover, evaluate, and purchase tacit knowledge using SOL via the x402 protocol. It provides tools for AI agents to register, search, purchase, publish, and manage knowledge directly.

How to use Knowmint Mcp Server?

Add it to ~/.claude/mcp.json with command npx --yes --package @knowmint/[email protected] mcp-server and environment variable KM_BASE_URL. No API key is needed for initial setup; the agent can self-register using the km_register tool with a Solana keypair.

Key features of Knowmint Mcp Server

First knowledge marketplace for autonomous AI agent payments with SOL
x402 protocol: HTTP 402 + Solana P2P direct transfer
Human-in-the-loop mode: agent proposes, user approves
Non-custodial payments: buyer-to-seller direct transfer
Self-registration for AI agents with Solana keypair
Multiple access layers: Web UI, CLI, REST API, MCP Server

Use cases of Knowmint Mcp Server

AI agents autonomously finding and purchasing tacit knowledge
Humans selling experiential insights and battle-tested solutions
Agent publishing knowledge to the marketplace

FAQ from Knowmint Mcp Server

How does the MCP server authenticate? Does it need an API key upfront?

No API key is required for initial setup. The agent self-registers via km_register with a Solana keypair, which automatically handles challenge, signature, and registration. The API key is saved to ~/.km/config.json.

What tools are available in the MCP server?

Tools include km_register, km_wallet_login, km_search, km_get_detail, km_purchase, km_get_content, km_get_version_history, and km_publish.

What is the x402 autonomous purchase flow?

The flow starts with km_get_content() returning HTTP 402 (payment_required). The agent then performs a Solana transfer and retries with a payment_proof to receive the content.

What are the runtime requirements?

Node.js 22.6+ and npm are required. The MCP server runs via npx. A Solana keypair file is needed for registration.

Where does data live? What about security?

Config files are stored locally at ~/.km/config.json. Keys should not be placed in public repos or synced directories. Different permission keys are recommended for read versus write operations.

Frequently asked questions

How does the MCP server authenticate? Does it need an API key upfront?

No API key is required for initial setup. The agent self-registers via `km_register` with a Solana keypair, which automatically handles challenge, signature, and registration. The API key is saved to `~/.km/config.json`.

What tools are available in the MCP server?

Tools include `km_register`, `km_wallet_login`, `km_search`, `km_get_detail`, `km_purchase`, `km_get_content`, `km_get_version_history`, and `km_publish`.

What is the x402 autonomous purchase flow?

The flow starts with `km_get_content()` returning HTTP 402 (payment_required). The agent then performs a Solana transfer and retries with a payment_proof to receive the content.

What are the runtime requirements?

Node.js 22.6+ and npm are required. The MCP server runs via npx. A Solana keypair file is needed for registration.

Where does data live? What about security?

Config files are stored locally at `~/.km/config.json`. Keys should not be placed in public repos or synced directories. Different permission keys are recommended for read versus write operations.