Skip to main content
The lab exposes its documentation as read-only MCP servers, so AI agents can search and cite the source material directly instead of guessing.

​
Lab hub — mcp.uzenlabs.com

A unified endpoint aggregating the docs manifests published by the lab’s properties:
Streamable HTTP, no authentication, read-only. Send MCP requests to the root path; sources are refreshed automatically as the underlying sites redeploy.

​
Onchain Diary

Full content library — research articles, the glossary, and hub pages, in English and Chinese:
Same protocol: streamable HTTP, no auth, read-only. Tools include content search, article reading, and glossary lookup.

​
Tool-bundled servers

Two projects ship their own MCP servers as part of the product:
  • ZensInk — the CLI includes an MCP server exposing every tool: python3 -m zens_ink.mcp. See ZensInk.
  • Margin (LiteInk theme) — the theme bundles a theme-aware MCP server with component, content-schema, and config tools, plus /.well-known/mcp.json for auto-discovery. See github.com/Liteink/margin.

​
House rules

All lab MCP servers are read-only. If you need write access to something, that’s a conversation, not an endpoint.