One note on the MCP server we also shipped (github.com/lemmaoracle/lemma/tree/main/packages/mcp):
x402 is already agent-callable at the protocol level, so no MCP wrapper is needed for payments. The MCP server exposes the read side of the same trust layer (query verified attributes, get schema, get circuit, get generator, get proof status) for agents in MCP-native environments (Claude Desktop, Cursor, etc.) that want to read from Lemma without a custom REST integration.
Two surfaces, one trust layer:
x402 : payment rail + ZK proof bundle in PAYMENT-RESPONSE
MCP : read interface for MCP-native agents
Large projects can monetize in other ways. It's best for small but technically essential libraries. e.g., like vue-xxx, rollup and moment. By issuing a new token, it is possible to monetize without changing the license while keeping OSS free.( https://medium.com/devtoken/dev-tokens-for-oss-a63e55c60e6b )
I switched from Flow to TypeScript.
Flow has some type-declared libraries, but it's fewer than TypeScript type-declared libraries. The excellence of VSCode also helps me.
OSS's sustainability has a significant challenge.
I think the token economy might solve it. I started experiments with npm.
https://devtoken.rocks/alpha/en
x402 is already agent-callable at the protocol level, so no MCP wrapper is needed for payments. The MCP server exposes the read side of the same trust layer (query verified attributes, get schema, get circuit, get generator, get proof status) for agents in MCP-native environments (Claude Desktop, Cursor, etc.) that want to read from Lemma without a custom REST integration.
Two surfaces, one trust layer: x402 : payment rail + ZK proof bundle in PAYMENT-RESPONSE MCP : read interface for MCP-native agents