GM people, and welcome to the fifth issue of “The ContextVM World”, your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!

In today’s update we cover the latest news from ContextVM. In particular, we have been chosen to mentor the next generation of open-source contributors through the Summer of Bitcoin internship program. We also cover our latest modification to the CVM website and the spam attack that recently hit our relays.

We also discuss the latest news from the ecosystem, with a growing number of MCP servers appearing. For example, two new MCP servers are now available through CVM, one based on am-i.exposed, another on OpenTimeStamp.

Moreover, we will present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.

Finally, we will bring the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!

Let’s start!

News from ContextVM 📰

A list of updates, releases and new cool features.

• Summer of Bitcoin: CVM has been invited to participate in the Summer of Bitcon (SoB) project, a global, online summer internship program focused on introducing university students to Bitcoin, Nostr, and open-source development. CVM will provide projects for students to work on during the summer, mentoring the new generation of open-source contributors and helping them bootstrapping their careers in the space. Do you have a CVM-based project you would like to propose for SoB? Feel free to reach out to us!

• Search by npub: We recently made a powerful update to our website to improve server discoverability and strengthen decentralization. Users can now lookup MCP server directly by npub and nprofile either in the search bar or directly by adding it to the URL. Bonus point, you can also search it through its NIP-05 identifier!

• Spam attack: We recently suffered a spam attack on our relays. To fix the issue and reduce the attack surface for the future, we decided to fork the Strfry relay, which is the base of our infrastructure, to add additional write policies to restrict accepted event kinds to the subset used by our relay.

News from the ContextVM Ecosystem 🗞️

Find all the projects leveraging ContextVM on ContextVM/awesome.

• Am I exposed?: A new MCP server is now available on Nostr leveraging the am-i.exposed on-chain scanner capabilities to audit the privacy of your wallet information, ranging from transaction evaluation, UTXO hygiene, and full audit. We also did a quick demo on how to use it.

• Time-stamping Nostr events: Another new MCP server is now available, allowing users to use OpenTimeStamp to time-stamp any Nostr event. The tool is very simple, providing one command to create an attestation and another to verify it. We also wrote a simple note with the instruction to use this server through CVMI CLI.

• Nostr.watch + CEP-8: Nostr.watch, an important online tool that monitors relays health, recently integrated CEP-8 payments in their CVM-enabled MCP server. Check Sandwich, nostr.watch creator, note to know more.

• Relatr + Ants: Relatr was recently added into the Advanced Nostr Text Search (Ants) project by Gigi to improve its search capabilities.

• New Relatr domain: Due to some issues with our registrar we no longer control the old relatr.xyz domain. You can now find it on relatr.net.

What’s Next for ContextVM? ⏭️

Let’s take a look at the features currently being implemented!

• CEP-15: This enhancement proposal implements a standard for defining and discovering common tool schema. This aims to enable interoperability between multiple servers, standardizing tool interfaces that clients can recognize and use consistently. It leverages MCP’s _meta field, RFC 8785 for deterministic hashing, and CEP-6 announcements for discovery, creating a marketplace where users can choose between multiple providers implementing the same standard tool interface.

• Three new CEPs have been proposed and are waiting for a number to be assigned:

  • CEP-XX: This enhancement proposal aims to define a way to detect when a message can’t be published, due to its payload exceeding the size limits of a relay. The linked issue tracks exploratory work for this new mechanism.

  • CEP-XX: This enhancement proposal aims to standardize the way in which MCP servers publish a persistent public profile and how they manage a public communication channel for updates and announcements.

  • CEP-XX: This enhancement proposal aims to standardize how users attach comments and reviews to server announcements. This would allow to create a Nostr-native review and discussion layer around servers.

Who is Talking about ContextVM? 📢

A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.

• CVM has been mentioned on Nostr Compass #15, a weekly newsletter covering everything going on in the Nostr ecosystem. CVM has been also mentioned in the Nostr Compass Podcast #12.

Interesting resources from the web 🤖

A curated list of resources we found interesting.

• Nicholas Carlini - Black-hat LLMs | [un]prompted 2026: Nicholas Carlini, Research Scientist at Anthropic, discusses how LLMs can now be used to automate attacks that were previously only doable by human adversaries.

• Thoughts on slowing the fuck down : An interesting article by Mario Zecher diving into what could be the best way to work with coding agents.

• Skills Over MCP Interest Group - March 24th 2026 Office Hours Notes: This resource provides the minute of the meeting of the Skills Over MCP Interest Group, the committee responsible for discussing the next steps, issues, and blockers for implementing Skills into MCP.

Find out more about ContextVM:

• Check out our website for documentation, blog posts, and more.

• Join our Signal group

• Follow ContextVM on Nostr

• Subscribe to our Substack. Help us spread the word!

• Check out our GitHub repositories and leave us a ⭐

GM people, and welcome to the third issue of “The ContextVM World”, your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!

In today’s update we cover CEP-17, the latest specification change to the CVM protocol. This change allows MCP servers to announce the relays for establishing connections, making it easier to be discovered by clients.

We also discuss the latest news from the ecosystem and the latest feature being implemented in the CVM protocol, CEP-15, for common tools schema.

Moreover, we will present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.

Finally, we will bring the latest news from the MCP ecosystem, including specification changes and new protocol additions. CVM is built on MCP, which means that we care about providing you up-to-date information from its thriving ecosystem.

Let’s start!

News from ContextVM 📰

A list of updates, releases and new cool features.

• Become discoverable: We recently merged CEP-17, a proposal that defines a relay list mechanism based on NIP-65 conventions. Servers can publish the list of relays they are connected to using kind 10002 events, allowing clients to discover the appropriate relays for establishing connections. This solves the current limitation where users must know both a server’s public key and its relay URLs to connect.

• A new release family for the CVM SDK: We published a new release family of the CVM SDK, v0.7.x. Notably, we introduced support for CEP-17 in v0.7.0, while successive patch releases introudeced new features, such as default discovery to bootstrap relays.

• Making the CLI agent-friendly: We rolled out several new improvements to our CLI tool, CVMI, bringing v0.2.x to life. This new release family introduces two new powerful commands:

  • call: This command allows users to invoke CVM server directly from the command line, making it highly suited for agentic use. It also reduces token usage, thanks to simpler and cleaner responses;

  • discover: This command allows users to easily find public CVM servers, by querying relay announcements.

• A new CVM SDK in Rust: Open-source contributor K0sh is currently doing a complete rewrite of the CVM SDK using Rust, the most common programming language in the Bitcoin/Nostr ecosystems. The project is still highly experimental, thus we recommend testing it taking great care.

News from the ContextVM Ecosystem 🗞️

Find all the projects leveraging ContextVM on ContextVM/awesome.

• Schlaus Kwab integrated an AI agent chat into earthly.city, a Nostr-native collaborative mapping application that leverages CVM. Check this note to view how it works!

What’s Next for ContextVM? ⏭️

Let’s take a look at the features currently being implemented!

• CEP-15: This enhancement proposal implements a standard for defining and discovering common tool schema. This aims to enable interoperability between multiple servers, standardizing tool interfaces that clients can recognize and use consistently. It leverages MCP’s _meta field, RFC 8785 for deterministic hashing, and CEP-6 announcements for discovery, creating a marketplace where users can choose between multiple providers implementing the same standard tool interface.

Who is Talking about ContextVM? 📢

A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.

• Our latest article on CVMI, the swiss army knife CLI for ContextVM.

• CVM has been mentioned on Nostr Compass #12, a weekly newsletter covering everything going on in the Nostr ecosystem.

Intresting resources from the web 🤖

A curated list of resources we found interesting.

• Google Workspace CLI: A one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more, with AI agent skills.

• MCPorter: A TypeScript runtime, CLI, and code-generation toolkit for MCP.

• Context Mode: An MCP server that allows to reduce context usage by 98%.

• CLI vs MCP: An interesting blog post hightlightin the difference between CLIs and MCPs.

• Code Mode: An MCP server that provides a technique for reducing context window usage during agent tool use.

• When the Interface Flattens Into a Prompt: This video explores emerging paths in AI interface design, and why terminal-like experiences are appealing and can be dangerous.

• The lethal trifecta for AI agents: This article explores the security risks of letting agents leverage tools that can lead attackers to steal you data.

• MCP is Dead; Long Live MCP!: A thoughtful blog post trying to shine some lights on the current hype on CLIs replacing MCPs.

Find out more about ContextVM:

• Check out our website for documentation, blog posts, and more.

• Join our Signal group

• Follow ContextVM on Nostr, nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm

• Subscribe to our Substack. Help us spread the word!

• Check out our GitHub repositories and leave us a ⭐

GM people, and welcome to the third issue of “The ContextVM World”, your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!

In today’s update we cover ephemeral gift wraps, which have been recently merged into the protocol with CEP-19. This feature introduces an optional convention for CVM servers and clients to exchange encrypted messages using an ephemeral gift wrap kind. We also present the latest release family, v0.6.x.

We also discuss the latest news from the ecosystem, with a new MCP server to query Wolfram Alpha over Nostr, and the new feature being implemented in the CVM protocol, namely CEP-15, for common tools schema, and CEP-17, which provides a way for a server to publish its relay list.

Moreover, we will present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.

Finally, we will bring the latest news from the MCP ecosystem, including specification changes and new protocol additions. CVM is built on MCP, which means that we care about providing you up-to-date information from its thriving ecosystem.

Let’s start!

News from ContextVM 📰

A list of updates, releases and new cool features.

• Ephemeral gift wraps are live on CVM: We recently merged CEP-19 proposal, which introduces an optional convention for CVM servers and clients to exchange encrypted messages using an ephemeral gift wrap kind. This is a major upgrade that provides more privacy in the communication between servers and clients, since it prevents relays to store the events.

  Consequently, we also open a PR in the NIPs repository. The proposed modification aims to expand NIP-59 to include the convention for ephemeral gift wraps.

• A NIP for CVM: Recently, we opened another PR on the NIP repository to formalize CVM as a minimal convention for transporting Model Context Protocol (MCP) JSON-RPC messages over Nostr. The proposal is waiting for feedback and reviews from other peers.

• A new major release family for the CVM SDK: With the merging of CEP-19, we released a new major version family for the CVM SDK, v0.6.x.

  Notably, v0.6.0 integrates support for ephemeral gift wraps, while maintaining compatibility with previous versions. We also released a patch version, v0.6.1.

  Previously, we released v0.5.0, which added a single paymentPolicy hook to make payment consent programmable.

News from the ContextVM Ecosystem 🗞️

Find all the projects leveraging ContextVM on ContextVM/awesome.

• Relatr has been running for more than two weeks without missing a single beat. No crashes, no downtime. It just worked!

• Wolfram Alpha is now available as a decentralized MCP server through CVM. Ask math, science, weather, conversions and more. Connect to the server here to test it out!

What’s Next for ContextVM? ⏭️

Let’s take a look at the features currently being implemented!

• CEP-15: This enhancement proposal implements a standard for defining and discovering common tool schema. This aims to enable interoperability between multiple servers, standardizing tool interfaces that clients can recognize and use consistently. It leverages MCP’s _meta field, RFC 8785 for deterministic hashing, and CEP-6 announcements for discovery, creating a marketplace where users can choose between multiple providers implementing the same standard tool interface.

• CEP-17: This enhancement proposal defines a relay list mechanism based on NIP-65 conventions. Servers can publish the list of relays they are connected to using kind 10002 events, allowing clients to discover the appropriate relays for establishing connections. This solves the current limitation where users must know both a server’s public key and its relay URLs to connect.

Who is Talking about ContextVM? 📢

A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.

• Our Hacker News post, presenting ContextVM to the broader technical ecosystem. We are actively working to get more eyes on out project!

• CVM has been mentioned on Nostr Compass #11 , a weekly newsletter covering everything going on in the Nostr ecosystem.

• Travis Knot wrote an article describing CVM as a protocol for creating “permissionless digital lemonade stands”. With CVM, you do not need permission to build!

• Our NIP proposal was mentioned in Nostr Biweekly Review (15-28 Feb 2026).

• CVM has been mentioned in the Financial Freedom Report #110 by the Human Rights Foundation (HRF).

News from the MCP world 🤖

What is going on in the MCP world?

• The Skills-over-MCP Interest Group is actively working to provide directions and guidelines on the possibility to provide Skills to agents as MCP resources. Contributors are focusing on the so-called skills-as-instructors, those that teach an agent how to use MCP tools correctly, without executing any code, with the aim to find a common ground to address distribution, portability, security and fragmentation. It is possible to find more information in the meeting notes.

Find out more about ContextVM:

• Check out our website for documentation, blog posts, and more.

• Join our Signal group

• Follow ContextVM on Nostr, nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm

• Subscribe to our Substack. Help us spread the word!

• Check out our GitHub repositories and leave us a ⭐

GM people, and welcome to the second issue of “The ContextVM World”, your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!

In today’s update we are going to discuss payments on CVM, enabled by CEP-8 specifications. The latest releases of CVM SDK and CVMI have been updated to support this huge milestone.

We will also cover the latest features currently being implemented. In particular, we will take a look at CEP-17, which deals with relay lists, and CEP-19, which aims to improve privacy for encrypted communications.

We will also present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.

Finally, we will bring the latest news from the MCP ecosystem, including specification changes and new protocol additions. CVM is built on MCP, which means that we care about providing you up-to-date information from its thriving ecosystem.

Let’s start!

News from ContextVM 📰

A list of updates, releases and new cool features.

• ContextVM has received support from OpenSats: OpenSats announced its fifteenth wave of grants from the Nostr Fund. ContextVM is one of the new projects to receive the grant, which will support core protocol development, SDK expansion, and improvements to the reliability of shared infrastructure. It will also allow the team to work on new SDK implementations, create and manage one-click deployment packages, provide comprehensive documentation and tutorials, and integrate CVM with open-source developer tools.

• Payments are finally live on CVM: With the recent merging of CEP-8 specification, anyone running a MCP server can finally monetize its capabilities, allowing for a decentralized and permissionless marketplace of services and tools. Most importantly, it does so without imposing a single (or a set of) payment method(s), but by standardizing the way users ask for payments.

  CEP-8 introduces a language called Payment Method Identifier (PMI), based on the homonymous W3C standard, that allows to define the specific payment method to be used during the interaction. In other words, PMI is the type-tag for the payment request payload, analogous to content-type in HTTP. For example, a BOLT11 lightning payment will be identified by the string bitcoin-lightning-bolt11. Notably, CEP-21 has been added to provide recommended naming conventions for new PMIs.

• CVMI latest release: v1.10.0 for CVMI, the cli tool for CVM, has been recently released. The latest version introduces comprehensive documentation for implementing payments through CEP-8. It also adds support for environment variables to spawned MCP servers and normalizes quoted command strings to serve any MCP server.

• CVM SDK release family 0.4.x: Starting from v0.4.0, the ContextVM SDK added support for payments through CEP-8. Other patch versions has been released to fix minor issues or include small features, such as payment export and logging and preventing zombie publishing loops. Notably, v0.4.5 added support for payments through NIP-57 Lightning Zaps. This is the third payment processor to be supported in CVM, following NWC and LNBits implementations.

  The release v0.4.6, adds notifications for payment verification based on NIP-47 NWC. Since this feature is not supported by all NWC providers, the payment processor will determine compatibility and only enable notifications if the provider supports it. Before publishing v0.4.6, we have released a series of patches which add deduplication capabilities for multi-relay deployments, making the transports more efficient and increasing performances when connected to multiple relays.

News from the ContextVM Ecosystem 🗞️

Find all the projects leveraging ContextVM on ContextVM/awesome.

• Agents are starting to realize ContextVM exists and are looking for ways to integrate it into their operations. Clawstr and The Colony are two examples of platforms where agents are discussing about the benefits of ContextVM.

What’s Next for ContextVM? ⏭️

Let’s take a look at the features currently being implemented!

• CEP-15: This enhancement proposal implements a standard for defining and discovering common tool schema. This aims to enable interoperability between multiple servers, standardizing tool interfaces that clients can recognize and use consistently. It leverages MCP’s _meta field, RFC 8785 for deterministic hashing, and CEP-6 announcements for discovery, creating a marketplace where users can choose between multiple providers implementing the same standard tool interface.

• CEP-17: This enhancement proposal defines a relay list mechanism based on NIP-65 conventions. Servers can publish the list of relays they are connected to using kind 10002 events, allowing clients to discover the appropriate relays for establishing connections. This solves the current limitation where users must know both a server’s public key and its relay URLs to connect.

• CEP-19: This enhancement proposal introduces an optional convention for CVM servers and clients to exchange encrypted messages using an ephemeral gift wrap kind. This CEP aims to improve privacy for encrypted communications by establishing a new kind 21059, similar to kind 1059, which will not be stored by a relay.

Who is Talking about ContextVM? 📢

A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.

• Our blog post providing a simple and fun tutorial to illustrate how the CEP-8 payment flow works. Get your Nostr badge now!

• Our blog post on CEP-8 and Digital Lemonade Stands.

• A note on our official Nostr profile highlighting the importance of CVM in an agent-mediated world.

• A note from MaximumSats, developer of the LNBits processor in the CVM SDK, discussin MCP-to-Nostr bridges.

News from the MCP world 🤖

What is going on in the MCP world?

• PR2127 presents a draft specification, SEP-2127, that proposes a standardize way to describe MCP servers, called Server Cards. This would allow an MCP client to discover server capabilities using a .well-known endpoint, without the need to establish a full connection.

  Note: This proposal together with the registry specification defines a series of HTTP endpoints attached to specific servers to allow discoverability of MCP servers. In ContextVM, we think this is an anti-pattern, increasing centralization and gatekeeping. We already solved discoverability in CEP-6 (Public Server Announcements) where we standardized the usage of relays as decentralized repositories. Servers are free to announce their existence in any number of relays and curation is done directly by the relays. This way, incentives are always aligned without any central point of failure.

• SEP-2133 has been officially formalized. This specification establishes a lightweight framework for extending MCP through optional, composable extensions. In particular, it provides guidance on how extensions should be proposed and adopted, and defines both a list of official extensions, developed and recommended by MCP maintainers, and one of experimental ones, for simple discovery, prototyping and collaboration.

• SEP-1730 has officially landed, providing a tier system for MCP SDKs. This allows to establish clear expectations for feature support, maintenance commitments, and quality standards. The specification defines a three-tier system, based on objective, measurable data. In particular:

  • Tier 1: Fully supported. The SDK implements the full protocol and is well supported;

  • Tier 2: Commitment to be fully supported. The SDK is actively working towrds full support;

  • Tier 3: Experimental. The SDK is in its early stage.

Find out more about ContextVM:

• Check out our website for documentation, blog posts, and more

• Join our Signal group

• Follow ContextVM on Nostr

• Check out our GitHub repositories and leave us a ⭐

GM people, and welcome to the first ever issue of “The ContextVM World”, your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!

In our updates we will bring you the latest information about CVM and its ecosystem, with a particular focus on projects, services, and companies leveraging it for their infrastructure.

We will also present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.

Finally, we will bring the latest news from the MCP ecosystem, including specification changes and new protocol additions. CVM is built on MCP, which means that we care about providing you up-to-date information from its thriving ecosystem.

Let’s start!

News from ContextVM 📰

A list of updates, releases and new cool features.

• The new v0.2.x family release of the ContextVM SDK has been announced on Wednesday 21st, focusing on reliability, code quality, and architectural maturity. This release transforms ContextVM from a functional prototype into a hardened foundation ready for long-running servers. While this release lays the groundwork for future enhancements, it provides backward compatibility with the previous release to allow for a smooth transition. We recommend upgrading any production environment to v0.2.x to benefit from the reliability improvements on relay handling and memory management.

• We announced the release of ContextVM Interface (CVMI), a CLI tool that aims to simplify development on ContextVM. The tool comes with a complete set of agent skills that cover the entire stack, from protocol fundamentals to production deployment. CVMI will soon become the go-to toolkit for everything related to CVM development, superseding older tools and integrating new features.

• Today we consolidated the old gateway-cli and proxy-cli tools into CVMI, simplifying the installation and configuration process. Two commands were introduced, serve to allow anyone to serve any MCP server over Nostr, even remote HTTP ones, and use to leverage remote servers as if they were local. Both new commands work out of the box with ephemeral keys and default relays, with the possibility to customize the setup.

• We announced the release family v0.3.x, following improvements to the gateway module. This component now allows users to expose remote HTTP MCP servers over Nostr.

News from the ContextVM Ecosystem 🗞️

Find all the projects leveraging ContextVM on ContextVM/awesome.

• Following our recent introduction of Trusted Assertions on Relatr, the specification has been officially merged in the Nostr protocol under NIP-85. This NIP allows users to offload Web-Of-Trust calculations, which require a huge amount of events and computational power, to declared trusted service providers, and for these providers to publish signed “Trusted Assertion” events for the client consumption. We published a blog post talking about the details of this integration in Relatr, and how request/response pattern and TAs are complementary.

• Relatr v0.1.16: Implemented relay capping and updated rate limit token defaults for better burst capacity. Upgraded to the latest version of the ContextVM/SDK.

• wotrlay v0.2.5: The web-of-trust Nostr relay implementation has been updated, bringing various improvements such as better error handling and enhanced observability.

• In a recent conversation with Pete Winn, the creator of nanalytics, a plethora of experiments over CVM, and games over Nostr like Word5, we learned that his CVM servers are currently receiving thousands of requests. Here, CVM acts as the imperceptible backbone of these applications. Good technology is invisible. On our side, Relatr is also receiving a high load of requests each day. This kind of load allows us to stress-test CVM and reveal bugs. All the gathered information is currently being used as the foundation for release family 0.2.x, which makes long-running servers with loads of requests stable and performant. CVM is still young and is maturing, becoming more stable and resilient in each iteration.

• Earthly.city is a project leveraging CVM for its integration with geographical data. The server is public and you can use it as well.

• More and more projects are currently joining the CVM world. If you are building something on top of CVM, please just let us know! We will be happy to assist, and include you in this newsletter.

What’s Next for ContextVM? ⏭️

Let’s take a look at the features currently being implemented!

• CEP-8: This enhancement proposal provides a standardized pricing mechanism and payment flow for MCP capabilities over CVM. This would allow servers to advertise pricing for their services, and enable clients to discover and pay for MCP capabilities.

• CEP-15: This enhancement proposal implements a standard for defining and discovering common tool schema. This aims to enable interoperability between multiple servers, creating a marketplace of service providers using the same tool interface.

Who is Talking about ContextVM? 📢

A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.

• Say WOT — Ep. 2: Avi Burra from Plebchain Radio sits down with Gzuuus to discuss CVM and the Web-Of-Trust tech stack.

• What’s next for Relatr?

• An interesting note about earthly.city, a project leveraging CVM.

• Trusted Assertion in Relatr

• SEC-05: YOLO Report

News from the MCP world 🤖

What is going on in the MCP world?

• MCP maintainers announced the release of MCP Apps, an official MCP Extension that allows any tool to return interactive UI components, such as dashboards, forms, and workflows, all rendered directly in the conversation. As of today, MCP Apps are already available in Goose, Claude, VS Code, and ChatGPT.

• A new functionality called “Tool search tool” is available in beta through the Claude APIs. This tool allows servers to reduce token usage by enabling dynamic tool discovery and the possibility to load them on-demand, thus reducing context window consumption and improving tool selection.

• In a recent blog post about the future of MCP transports, Kurtis Van Gent and Shaun Smith discussed the advantages of making the MCP protocol stateless. Interestingly enough, CVM added a stateless mode a couple of months ago, allowing efficient communication between clients and servers. Now, the same concepts are coming to the official MCP specifications.

Find out more about ContextVM:

• Check out our website for documentation, blog posts, and more

• Join our Signal group

• Follow ContextVM on Nostr

• Check out our GitHub repositories and leave us a ⭐