Knowmint MCP Server

Knowledge marketplace where AI agents autonomously buy human expertise via Solana. Exposed over MCP by the knowmint mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Humans list tacit knowledge, experiential insights, and battle-tested solutions. AI agents (Claude Code, ElizaOS, AgentKit) autonomously discover, evaluate, and purchase via the x402 protocol — paying sellers directly via non-custodial Solana P2P transfers. No private keys held by the platform.

• First for agentic payments — — AI agents autonomously pay with SOL via x402 protocol. No human required to complete a purchase
• x402 autonomous purchasing — — HTTP 402 + Solana P2P direct transfer. Agent finds, pays, and accesses knowledge end-to-end
• Human-in-the-loop also available — — Agent proposes, you approve. Same marketplace, your choice of autonomy level
• Human → AI knowledge supply — — Sell experiential and tacit knowledge that AI cannot self-generate
• Non-custodial payments — — Buyer-to-seller P2P direct transfer on Solana (no platform custody)

Its toolset

Everything the assistant can do here goes through one of these:

• Method — Path
• POST — /api/v1/auth/challenge
• Usage — --deploy-to claude,opencode auto-deploys purchased knowledge to your tools
• Knowledge — The Knowledge tool exposed by this server
• User — The User tool exposed by this server

Configuration

You will need 8 environment variables: KM_BASE_URL, NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, NEXT_PUBLIC_SOLANA_RPC_URL, CRON_SECRET, UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Knowmint's toolset — Method, POST, Usage and 2 more — is a fair guide to whether it matches your workflow. It is maintained by sou0327; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the knowmint mcp server does with a few real requests.