New informational CEP has dropped! This is CEP-35, which standardizes functionality already present in our TypeScript SDK, specifically, stateless operations. Typically, MCP servers and clients use an initialization lifecycle to negotiate capabilities. However, if you don’t need a long-lived session with a server, or if you already know the server’s supported capabilities, this lifecycle introduces unnecessary overhead. Stateless mode addresses this by allowing clients to make one-shot requests to servers. It’s lighter, reduces roundtrips, and simplifies interactions. While this functionality has been available for some time, we wanted to standardize it further as we advance the Rust SDK. This ensures parity and sets clear expectations and conventions across different implementations. Read more in the CEP-35 spec:

ContextVM Documentation

CEP-35 Stateless Session Discovery and Capability Learning

Informational guidance for session-scoped discovery exchange, stateless behavior, and capability learning

New issue of the CVM world newsletter. This time we cover the latest news from ContextVM. In particular, we discuss the recent merging of two new specifications, CEP-23, which allows servers to publish a public profile and post notes signed with the same keypair used for protocol operations, and CEP-24, which allows users to attach comments and reviews to servers. Please if you enjoy this issues consider subscribing to our substack

The ContextVM World 🌍 | Substack

Your biweekly appointment with ContextVM, MCP, and Nostr. Click to read The ContextVM World 🌍, a Substack publication. Launched 2 months ago.

View article →

We've just merged CEP‑24 🚀 This standardizes how NIP‑22 can be used to leave reviews attached to server announcements (https://docs.contextvm.org/spec/ceps/cep-24/). This provides a simple way for users to publish their experiences with the servers. Together with CEP‑23, which standardizes how servers can leverage profile‑metadata events (kind 0) and notes (kind 1), the circle is now complete. Server operators can now maintain a social presence interoperable with any Nostr client, and they can receive and answer reviews directly on their servers. This makes the ecosystem more participatory and helps operators and users stay in contact. In addition, we have deployed an implementation of reviews on the https://contextvm.org website. Let's keep building! 🚀🚀

At ContextVM we believe in protocols over platforms. We believe in cryptographic keys over accounts. We believe in direct value exchange over third-party intermediaries. Your infrastructure, your rules.

A large part of the latest updates was thanks to the SoB students. Thanks, guys you rock! 🔥

We continue shipping! A new version of the CVMI CLI, 0.3.0, is available. This time we integrated the last sparse CLI that had not yet been included, CTXCN. The new command in CVMI is `npx cvmi cn`; the functionality is exactly the same then the previous CTXCN. Some minor bugs have been squashed, and the config‑file naming convention has changed to be more consistent with the 'cn' command. Apart from that, everything else remains the same. This is the final integration needed to bring all previous sparse CLIs into CVMI, making it truly the Swiss army knife for the CVM ecosystem 💪 To update, just run `npx cvmi@latest`.

This is also already integrated in https://contextvm.org Now servers that publish profile metadata will render a profile card in the sidebar. If the server has notes published, they will appear there as well. This is the Relatr server page, for example. View quoted note →

CEP-23 is now merged, and TS SDK 0.9.0 ships support for publishing server profile metadata (kind:0) directly from the Nostr server transport. This standardizes a pattern we were already seeing in the wild: servers using the same pubkey not only for protocol operations, but also for profile metadata and public social communication on Nostr. With CEP-23, servers can optionally publish kind:0 for human-friendly identity metadata and `kind:1` notes for updates, changelogs, and operator communication, without changing the existing discovery model. `kind:11316` remains the machine-readable capability surface. `kind:0` and `kind:1` add the social layer. A small addition, but an important step toward making ContextVM servers more legible, interoperable, and present across the wider Nostr ecosystem. CEP-23 + TS SDK 0.9.0 are live. Skills are updated as well. Happy building

ContextVM Documentation

CEP-23 Server Profile Metadata and Social Communications

Optional kind 0 metadata and kind 1 notes for server social presence on Nostr

The goal was clear: build a validation plugin system for Relatr that would let anyone write plugins easily, share them easily, install them easily, and distribute them natively through Nostr itself. View article →

At ContextVM we chose Nostr as a communication layer because its simple, permissionless, and decentralized. We think it’s one of the best possible technologies for AI agents to leverage MCPs.

Happening in about 10 minutes. View quoted note →

Do you want to know more about what ContextVM is, how it works, and what the recent developments are? Join our first community call, Thursday 16th @ 4PM UTC

HiveTalk

Hivetalk Honey Video Conference - Join ContextVM

This is a permanent room to chat about ContextVM, MCP, AI, Nostr

HiveTalk

CVM community call

CVM community call

Wow someone made a pod from the article we wrote yesterday for the new version of Relatr! This is awesome ♥

UnsaltedButter

Not watching? Stop paying.

View quoted note →

ContextVM TS SDK 0.8.0 is live, with CEP‑22 oversized‑payload transfer. Large payload delivery over Nostr relays is now much more robust. We even stress‑tested it by pushing a 1.5 MB image over regular relays, partly to check robustness and partly for fun :) It worked, but keep in mind that this is not a general‑purpose file transfer protocol If you run a server or client on the TS SDK, update to 0.8.0. The CVMI CLI was also bumped to include it. We keep pushing boundaries 🚀 If you are curious about the underlying specification you can read it here:

ContextVM Documentation

CEP-22 Oversized Payload Transfer

Bounded oversized payload transfer for ContextVM using progress-notification framing

Communications over the internet has been centralizing more and more since its very beginning, choked by permissioned control points. The risk we foresee is that the agentic web can fall in the same trap. ContextVM actively breaks this monopoly by routing the Model Context Protocol (MCP) over Nostr's decentralized relay network, leveraging censorship-resistant public keys that no single entity can shut down or revoke.

Curious about which services are already leveraging ContextVM? On our website you can find a list of public server to which your AI agent can connect through our infrastructure! 👇🏻 https://contextvm.org/servers

We bring amazing news! ContextVM has been invited to participate in the Summer of Bitcoin program.

Summer of Bitcoin

Summer of Bitcoin

A global, online summer internship program focused on introducing university students to bitcoin open-source development and design

This is a global, online summer internship program focused on introducing university students to Bitcoin, Nostr, and open-source development and design. We’re very glad to have been chosen as mentors. We’d also be grateful to hear your project ideas for a student to work on for ContextVM during the summer. Please share any you have. What would you like to see in ContextVM?

🚀 https://contextvm.org/s/nprofile1qyd8wumn8ghj7un9d3shjtnrdah8getcw3mx6tn0wfnj7qpqvk3nfvp0tyfu7tqlwvmkq3xlzyj5zen8de75n8gvxn3v5yx08ctq06sg4p View quoted note →

Setting up an MCP server to be used by AI agents requires a lot of skills, managing domains, OAuth, port forwarding. ContextVM changes the game, reducing the burden for running a remote MCP server!

Thanks for the help reposting this; we got some new subs :)  really appreciate it. View quoted note →