MCP Server — @uks/mcp-server
The UKS MCP server turns packets and the live Registry into tools that Claude (and any MCP client) can call directly. It's the fastest path from "verified knowledge" to "an agent that uses it."
npm install -g @uks/mcp-serverTwo ways to run it
Via the CLI (recommended)
uks serve my-packet.uks.jsonThis prints a claude_desktop_config.json snippet. Paste it into your Claude Desktop config and your packet — plus the public registry — become live tools.
Directly
Point any MCP client at the uks-mcp-server binary. It connects to the public registry with zero configuration (--offline or UKS_REGISTRY_URL=none opts out).
Tools it exposes
| Tool | What it does |
|---|---|
answer_pack | Returns graded, license-checked citations for a question — each with a fail-closed reuse_ok flag and the packet_id to pull |
search_registry_semantic | Semantic (embedding) search over the registry |
search_registry_hybrid | Hybrid search — semantic + full-text fused (RRF) |
| local packet tools | When you serve a file, its sources become directly queryable |
Every result carries its evidence grade, license, and freshness — and respects the registry's trust & safety vetoes, so an agent never silently consumes retracted, taken-down, or dead-link knowledge.
Stale-packet auto-refresh
When serving a packet, the server tracks a version baseline at pull time and refreshes when the registry copy changes (TTL-guarded; tune with UKS_STALE_MS).
→ Related: Query the Registry · Trust & safety · CLI