ContextVM

It is shipping time! 🚀 cvmi v0.4.0 is out!

The ContextVM CLI now speaks CEP-8 payments natively. Priced capabilities are first-class in the CLI:

💳 See prices upfront — cvmi call now shows advertised per-tool prices and accepted payment rails right in the tool list and --help.

🔀 Two payment modes:

• transparent (default for call) — PMI-agnostic settlement, the server picks the rail.
• explicit_gating — priced tools surface a clean Payment Required error with payment options. Pay one, retry, done. Now the default for cvmi use, so agent hosts over stdio get explicit signals instead of silent notifications.

🛡 Spec-hardened parser — malformed cap prices (negative values, out-of-order ranges) are now rejected per CEP-8, not coerced into bogus ranges.

⚙ cvmi serve gained payment interaction config.

Plus bumps to @contextvm/sdk ^0.13.9 and @modelcontextprotocol/sdk ^1.29.

Upgrade and start charging for your capabilities 🔌 npx cvmi@latest

#ContextVM #MCP #CEP8 #Bitcoin #Lightning #OpenSource

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

Make your MCPs over Nostr, composable, token efficient, easy 🚀

#mcp

🚀 Serve and Use: two new commands, one CLI, zero hassle

We merged our standalone gateway‑cli and proxy‑cli tools directly into cvmi. What used to require separate installations and configuration now lives under one unified CLI, and it couldn’t be simpler.

Serve any MCP server over Nostr:

• For example, the NostrBook: npx cvmi serve npx -y @nostrbook/mcp@latest
• Or even expose a remote HTTP server through Nostr👀👀: npx cvmi serve https://mcp.applesauce.build/mcp

This is a very new feature and led us to bump our SDK version to 0.3.x. More info is available in the CHANGELOG (https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md) and the gateway overview (https://docs.contextvm.org/ts-sdk/gateway/overview/).

Use a remote server and access it locally via stdio: npx cvmi use 7506...5fa3

Both new commands work out of the box with ephemeral keys and default relays. Override relays, keys, or other settings via flags, config files, or environment variables when you need more control. To see all available options, just use --help with any command.

For builders who want to ship, and for users who want to connect to their services easily, the toolkit is shaping well: skills, servers, and connectivity in one place. Run npx cvmi and explore. Soon we’ll add new features to complement these and give you everything you need to learn, build, debug, and interact with the CVM ecosystem. Stay tuned.

https://github.com/contextvm/cvmi

#ContextVM #Nostr #MCP #decentralized

🎇Meet CVMI: the Army knife we are building for ContextVM development🧑‍💻

If you are building/vibing on Nostr, this is for you. We are shipping CVMI alongside a complete skill set that makes ContextVM development delightful.

The skills cover the entire stack: protocol fundamentals, architecture concepts, client and server development, troubleshooting, SDK internals, and production deployment. Each skill includes working templates, reference documentation, and patterns distilled from real Nostr development. Everything you need to do is npx cvmi.

Or grab the skills through CVMI with npx cvmi add, or through the skills CLI with npx skills add contextvm/cvmi.

These commands will show you the list of available skills and guide you through their installation for any coding platform. Cool, right?

You can also pick exactly what you need npx cvmi add --skill overview

CVMI starts as a skills manager, but we are building toward the unified toolkit that ContextVM deserves. One CLI for skills, server interaction, dev tools, the works.

For builders who want to ship. The skills are here now.

https://github.com/contextvm/cvmi

If you don't know what skills are: https://agentskills.io/home

#ContextVM #Nostr #MCP #buildinpublic

The Circle is Now Complete ⥁💯

We're excited to announce that our main domain, https://dvmcp.fun, has been updated with the new version of the website! While it might look the same on the surface, under the hood, DVMCP has been completely refactored to implement the latest MCP specifications.

This update brings full support for all major MCP capabilities, tools, resources, and more. We've introduced different kinds for announcements and ephemeral events for client-server communication, enhancing design and efficiency.

Next inmediate thing in on our agenda is encryption for communication and private servers to boost user privacy, and the implementation of the ping capability to check server availability. We're also planning to deploy more servers with exciting use cases.

We're on a mission to make DVMCP the best it can be, and we need your help! If you're interested in contributing, please reach out.

Stay tuned for more updates, and thank you for joining us on this journey!

Read the full article https://dvmcp.fun/blog/circle-complete

#DVMCP #MCP #DVM

📢 Roll out news! 📢

Last week we released the new version of the dvmcp packages and gave dvmcp.fun a fresh update to match the latest specs. We've been testing it on next.dvmcp.fun and everything looks great!

Mark your calendars: we're rolling out the new website on the main domain in just two days (June 12th)! This means the current dvmcp servers on dvmcp.fun will not appear, as the new spec brings some breaking changes to kinds and events.

🛠️ Action Required for dvmcp users 🛠️

If you're running or consuming dvmcp servers, please update your packages to the latest version (0.2.x) to stay compatible:

• Server Operators: Update your dvmcp bridge to the latest version.
• Server Consumers: Update the discovery package to the latest version.

That's it! Just update, and the packages will take care of the rest. Let's make this transition smooth and hassle-free! 🚀

#dvmcp #mcp #llm

🌟 Release Time! 🌟

We’re thrilled to announce the new version of DVMCP! This update features support for the latest MCP specification, unlocking exciting possibilities and ensuring a future-proof design for the protocol.

🔧 Highlights:

• Full support for major MCP capabilities.
• Complete refactor of the dvmcp.fun website (currently at next.dvmcp.fun)
• New storage type for relays, enhancing ephemeral event handling.

Explore the available servers at next.dvmcp.fun and share your feedback/bugs over the next 10 days as we roll out new features to the main domain!

Read a more detailed article of this release at dvmcp.fun/blog/release-time

Thank you for joining us on this journey! Stay tuned for more updates! 🚀

#DVMCP #MCP #Nostr #Ai #LLM