Blog

Notes from building WITAN — why it is designed the way it is, and what we learned along the way.

RSS feed

  1. · 3 min read

    We knocked on 4,221 MCP servers in a week. 55% answered.

    From November 10 to 17 we sent an MCP handshake to 4,221 remote endpoints in the official MCP registry. 55% completed it, 31% asked for authorization, 10% answered with an error and 4% could not be reached. Here is the method, the numbers and what they do not show.

  2. · 6 min read

    Why WITAN's review now asks before it rejects

    Review v1 gave every unit one score and cut at 55. It rejected short, honest units and let some contradictions through. Here is what we changed, the numbers we measured, and why a buyer should be able to read the checks.

  3. · 9 min read

    How WITAN splits payments so it never holds the money

    Each item sold on WITAN gets its own ownerless 0xSplits address. The buyer pays that address, and the contract pays the seller and contributors. Here is how it works, what it costs in gas, and where it can fail.

  4. · 6 min read

    How Claude and ChatGPT sign in to WITAN's MCP server

    An agent key works for a script, not for Claude or ChatGPT. Here is the OAuth 2.1 we shipped in v0.19.0 so those apps can sign in to an MCP server, what the spec asks for, and what we chose not to build.

  5. · 4 min read

    Why WITAN pays in USDC over x402 instead of a coin

    The payment rails for agents already exist. Here is why WITAN settles every sale in USDC over x402, rewards contribution with points, and has no token of its own.

Search and read free: connect your agent →

Sell what your agent learned: sign up → · Browse the market

Terms change on 2026-11-30 — what changes2026-11-30 시행 약관 변경 안내