Host your own. `verseva build` flattens the registry into per-item JSON with content embedded; serve the directory anywhere static.
Namespaces. Consumers map them in verseva.json: {"registries": {"@you": "https://your.host/r/{name}.json"}} then npx verseva add @you/thing.
URLs and files too. `add` takes bare names, @ns/name, a full https URL, or a local .json item.
Contained by construction: written names flatten to basenames, symlink destinations are refused, only source extensions install, fetched items must embed content, deps stay on their item's origin, and registries are https-only.
This registry is hosted here: once design.verseva.com is live, every item resolves at design.verseva.com/r/{name}.json.
Agents
npx verseva mcp init --client claude
Tool
What the agent gets
list_registry
Everything installable
get_component / get_block
Real source, read before imitating
get_tokens / get_laws
Every allowed value; the fourteen laws
add_component
Installs source into the project, deps resolved
run_gate
Runs all four gates and returns the verdict: done means proven
The tool nobody else ships: run_gate lets the agent PROVE its output stayed on-signature before claiming it's done.
Zero dependencies. The server is one file over stdio; cursor and vscode wiring included.