Wrap any .kolm artifact in a Model Context Protocol server.
Claude, Cursor, Continue, and every MCP-aware agent discovers it without configuration.
Local first. Frontier as fallback. Receipts on every call.
# In a .kolm directory or pointing at a file $ kolm serve --mcp support-triage.kolm ● kolm v0.4 · serving support-triage.kolm ● mcp endpoint : http://127.0.0.1:7327 ● protocol : mcp/0.1 + sse ● tools exposed : triage, explain_label ● k-score gate : 0.70 (this artifact: 0.94) ● receipts : on (hmac, anchored to public registry)
Same task. Same prompt. The agent doesn’t know the difference. But the user’s phone, wallet, and threat model do.
No daemons. No control plane. Run the binary, agents see it. Stop the binary, they don’t.
kolm binds 127.0.0.1:7327 by default and writes a .well-known/mcp.json next to the artifact so any client on this machine can read its capabilities.
mDNS announces the service as _kolm._tcp.local for LAN-aware clients. No router config needed; loopback works fine for solo dev.
The artifact’s manifest signs a short-lived bearer token; clients exchange it on first connect. Every tool call returns a hmac-chained receipt.
Standard MCP over SSE. Tool schemas come straight from the artifact’s manifest — the agent sees exactly the surface kolm sealed in.
If your agent speaks MCP, kolm shows up. Three popular ones:
Drop the artifact path into claude_desktop_config.json. kolm-served tools appear in the next session.
"command": "kolm", "args": ["serve","--mcp","./support-triage.kolm"]
MCP server settings → add Local. Cursor’s agent picks up tool schemas and types them into the prompt automatically.
cursor add-mcp support-triage
Same shape: register a local MCP target, point at the artifact path. Continue auto-routes tool calls and surfaces receipts inline.
~/.continue/config.yaml
kolm prepends an X-Receipt header to every MCP response.
The receipt is a hmac chain over (source_hash, input_hash, output_hash, version_id, runtime_version, issued_at),
anchored to the public Kolmogorov registry. kolm verify
reproduces the chain offline. kolm verify --against registry
checks the upstream anchor — useful when an artifact is shared across machines.
$ kolm serve --mcp support-triage.kolm | jq '.receipts[0]'
{
"spec": "rs-1",
"source_hash": "9f1a…b3",
"input_hash": "ab02…7e",
"output_hash": "ef44…c8",
"version_id": "v0.1.4",
"runtime_version": "kolm/0.4.0",
"issued_at": "2026-05-07T03:14:00Z",
"hmac": "verified"
}