The cool part about the demo, ahead of the reduction in token usage compared to building this with the MCP interface, is the progressive disclosure. The LLM didn’t know anything about Earthly, Wolfram, or Relatr, and it discovered tools and usage as needed. No extra tool schemas were loaded unnecessarily, no bloated context window, just organic discovery and usage.

We’re thrilled to roll out CVMI CLI 0.2.x, adding two powerful commands: `call` and `discover`.

`call` lets you invoke CVM servers straight from the command line, perfect for debugging or plugging into agents. No MCP config or schema loading needed; responses are cleaned to save tokens. Save servers with aliases and run them like `npx cvmi call relatr`.

`discover` query relay announcements to list available tools, just run `npx cvmi discover`.

Demo: query Earthly and Wolfram for the Eiffel Tower’s address and height
https://video.nostr.build/14f2338be8a83b3e489233fbfcc359956eabb45d2ffee88417c72e1a0aaf7b4f.webm
Get Sovereign Engineering pubkey using Relatr.
https://video.nostr.build/e6560296c095847b5e5c20ea0d053f3c74bde4145f0ebe1f2bfd0a30721f85cf.webm

These upgrades make CVM servers far easier to use and compose, cut token costs versus MCP, and give developers a simple way to debug, script, or integrate CVM services from the command line.

Some screenshots of this new capabilities:

🚀 CEP-17 is now merged into ContextVM, and it is available in the ts SDK from v0.7.x.
https://docs.contextvm.org/spec/ceps/cep-17/

This is a meaningful step forward for resilience. With CEP-17, servers can publish the relay list they use following NIP-65, and clients can resolve connection paths more intelligently: first from explicit configuration, then from relay hints embedded in `nprofile`, and then if nothing is define from relay list discovery. That makes connectivity more robust by default, reduces dependence on central points of failure, and avoids hardcoded relays in normal client setup.

It also makes client configuration simpler. In many cases, you can now just pass an `nprofile` string and clients will use its relay hints directly; if those are not available, it can fall back to CEP-17 discovery through NIP-65 relay-list metadata.

The reference implementation is already in the SDK, the docs and skills have been updated, and contextvm.org now surfaces these new `nprofile` identifiers as well. Small change in surface, big improvement in how reliably clients can find and reach servers across a more sovereign network 🚀

We’re so back. DNS problems have been resolved, sites and relays are reachable again 🚀

We've been having problems with DNS and registrars, which is why our ContextVM websites are down. We have a pending transfer that should be resolved soon. In the meantime, we’ve deployed the main site and documentation on GitHub Pages as a backup alternative. The links are:

- https://contextvm.github.io/contextvm-site/
- https://contextvm.github.io/contextvm-docs/

Sorry for the inconvenience. CVM servers are still running, and clients can still connect using any relay, there’s no disruption there 🦾

Nostr == WS == CVM.
Connecting to servers, calling tools, etc, everything has worked over WebSockets since day one with ContextVM 🚀

A new issue of our biweekly newsletter is out! 🚀
"Ephemeral Is Better — The ContextVM World #3"
Available in nostr and substack:
https://contextvm.substack.com/p/ephemeral-is-better-the-contextvm
naddr1qvzq...