Our team is currently looking into CVM Bundles .cvmb, a packaging format to easily distribute servers and provide one-click deployment. The spec and implementation we are working on is inspired by .mcpb conventions by the official MCP working group https://github.com/ContextVM/cvmi/pull/4

ContextVM Rust SDK 0.2.0 is out! 🚀 MCP over Nostr just got a whole lot more capable. Three big things landed today: 📦 Oversized transfers (CEP-22) Until now, messages were capped by what fits in a single Nostr event (around 65 KB). Larger payloads, like big tool results or resources, now split into chunks automatically, get verified end-to-end, and reassemble on the other side. Servers only do this when the client supports it, so older clients keep working. 🌊 Open-ended streaming (CEP-41) A server tool can now send a live stream of data back to the client while a request is still running, think progress, partial results, or log lines. The client reads it as an async stream, and the final normal response still arrives at the end. Streaming is negotiated automatically with clients that support it. 🌍 UniFFI bindings, write ContextVM in your language The SDK now ships bindings for Python, Swift, Kotlin, and C/C++, all built on the same Rust core. That means native support on mobile, backend services, and scripting runtimes. There's a runnable examples/python/ folder to get you started. Plus: smarter relay resolution (CEP-17), richer server announcements (CEP-6), optional human-friendly server profiles (CEP-23), progress-aware request timeouts, and an MSRV bump to 1.88. Huge thanks to for the job on uniffi bindings, and for all the hard hork! Ready to build on this? Read the docs and ship your first ContextVM server or client today: https://docs.contextvm.org/

🚀 @contextvm/mcp-sdk 1.30.0 — 41% smaller bundles, opt-in validation New patch for our lightweight stdio-focused MCP SDK fork. Two lightweighting wins, zero protocol changes: 📦 Tarball: 2.4 MB → 1.2 MB (−50%) Dropped unreferenced CJS type declarations and source maps that were shipping but never used. 🗜 Consumer bundles: −41% gzip - Client + stdio: 90.4 → 53.1 KB - McpServer + stdio: 97.6 → 60.1 KB The big win: JSON Schema validation (ajv) is now opt-in. Most apps define tools with Zod (validated natively) but never actually validate the JSON Schema they receive over the wire, so they were shipping 37 KB of ajv for nothing. Now ajv only lands in your bundle if you explicitly need it. No breaking protocol changes. McpServer's own tool input/output validation is untouched. Existing apps that relied on default validation just need to pass the validator explicitly to re-enable it. ⚡ Smaller install, smaller apps, same CVM. Alongside this new release, we’ve published a new version of our TypeScript SDK (@contextvm/[email protected]), which includes this lightweight MCP SDK along with other fixes for open streams

Have you already tried our new website chat? This chat connects directly to MCP servers exposed through ContextVM, using your favorite LLM! https://contextvm.org/chat

We just got a PR merged into the official MCP Rust SDK! Contributing to upstream feels good man! 😎 https://github.com/modelcontextprotocol/rust-sdk/pull/858

We recently released a new version of our TypeScript SDK, v0.12.0! For this version, we forked the official MCP ts-sdk and stripped out all unnecessary dependencies for our project. Many features, such as HTTP transport are useless in ContextVM! Check it out! https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#0120

Also, if you want to chat, share, or clear any doubts, we have a group on Signal and also on Discord. Feel free to join! https://cordn.net/chat/3f5a6278-a38e-4079-840f-4e7523773f38?m=eyJuYW1lIjoiQ29udGV4dFZNIn0%3D https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR

We’ve just updated our documentation https://docs.contextvm.org to follow the https://diataxis.fr , which aims to bring more clarity and structure to it. We’ve also added documentation for the Rust SDK we recently released. Additionally, remember that we also have Skills to provide all necessary CVM documentation to LLMs. Happy building! 🚀

ContextVM makes it easier to deploy your self-hosted infrastructure. No domains, no OAuth, no port forwarding!

Spectr, a Nostr-powered client, is now powered by Relatr and ContextVM! Check out this video to see how it works!

And we have more news for today… hold on tight!

The latest issue of our CVM World is out, with so much news, this one is packed! 📦 If you like the work we’re doing, please consider subscribing to our biweekly newsletter. You could also contribute or donate some sats. Every little bit counts! 🫶 https://contextvm.substack.com/p/the-benefits-of-foss-the-contextvm

You can also use the SkateSpots server through the https://contextvm.org/chat interface 🛹

CEP-8 can now talk directly to AI agents. 🧵 With the just released ContextVM SDK 0.13.0 we're shipping full support for a new CEP-8 mode called Explicit Payment Gating. Why we built it: CEP-8 already let servers charge for their tools and capabilities, but only "behind the scenes", payment was handled silently by the transport layer. That's great for a wallet app. It's not great for an AI agent that actually needs to decide whether a call is worth paying for. The fix: Agents reason through normal MCP responses, so we turned payment into one. Now a paid call returns a clean "Payment Required" error (-32042) that carries human-readable instructions and one or more payment options. Feed that straight to your LLM, it reads the instruction, pays the invoice its own way, and retries the same call. No special SDK knowledge required, and it works with any MCP-compatible agent runtime. This design is based on the MPP spec and inspired by HTTP's 402 Payment Required status code, a long-reserved error code for exactly this idea, now adapted for JSON-RPC and AI agents. What it unlocks: - AI agents that natively understand and handle paid MCP capabilities - Per-call budgets and consent at the agent layer - Payment as a first-class decision: pay, decline, or escalate to a human Under the hood, each successful payment grants a single-use authorization that's matched to the exact same request on retry, and a "Payment Pending" error (-32043) keeps verification from spamming invoices. Fully backward compatible, the existing silent "transparent" flow stays the default, so nothing breaks for current users. Try it: Upgrade to @contextvm/sdk 0.13.0 and turn on a paid capability with explicit gating. Docs: CEP-8 spec — https://docs.contextvm.org/reference/ceps/cep-8/ Explicit gating guide — https://docs.contextvm.org/how-to/payments/explicit-gating/ API reference — https://docs.contextvm.org/reference/ts-sdk/payments/explicit-gating/ Go build something agents can pay for. 🔌 #ContextVM #MCP #AI #Bitcoin #Lightning #Nostr

This is also a great example of what CVM allows, a full CVM server running in a browser tab! 🤯

ContextVM makes it easier to deploy your self-hosted infrastructure — No domains, no OAuth, no port forwarding!