ContextVM

Just released an update to the ContextVM website. This one adds a search bar to easily filter servers or assist you in connecting to private servers. In the video, you can see how we test this by deploying an MCP server on a computer, taking its public key, and connecting and using it on a different machine—just that easy ✨ Also, all communication is encrypted and giftwrapped; no one can tell what is happening. Be your own infrastructure https://video.nostr.build/11ca4cf7e49f1fbc45004888a56a165ca65f124c2b14b2eb31f0953f4ac4a85e.webm

This is a beautiful table, isn't it? https://www.contextvm.org/faqs

We're thrilled to announce the launch of the new ContextVM website, live at https://contextvm.org ! 🚀 This marks a significant step in our mission to create a sovereign, resilient, and open marketplace for computational tools and services. The new site makes it easy to discover, connect to, and use ContextVM servers. Key features include: - Discover Public Servers: Explore publicly available ContextVM servers shared by the community. - Connect to Private Servers: Seamlessly connect to and use your own private servers from anywhere. Currently there are two public servers running: DuckDuckGo search to perform searches and fetch websites, and NostrBook MCP with documentation about nostr, nips, kinds and more. You can test them now, they are open to everyone Check out a short demo of the site: https://video.nostr.build/4a0f4498cadb8e165d96118ece0714d6c03f2b135d340871cc89567a5cf93195.webm Read more about the launch on our blog post: https://www.contextvm.org/blog/releasing-new-site The site includes a Blog, About page, FAQ, and dedicated documentation at docs.contextvm.org. The entire website is open source, built with Svelte 5 and the applesauce Nostr library. We welcome contributions from the community. We're also looking for talented designers to help shape the future of the ContextVM interface. If you have experience in UI/UX design and believe in a more open, permissionless internet, we'd love to hear from you. Get involved: * Explore the new website at https://contextvm.org * Contribute to the project on GitHub at https://github.com/contextvm * Join the conversation in our Signal group: https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR For any questions or help, please don't hesitate to get in contact.

nostr:npub1p4kg8zxukpym3h20erfa3samj00rm2gt4q5wfuyu3tg0x3jg3gesvncxf8 created HyperNote, which allows users to create interactive experiences embedded within nostr notes 🤯 These can be thought of as nostr mini-apps published as nostr notes 🤯🤯 It also demonstrates how ContextVM can be used to add custom interactive logic to a HyperNote, all embedded and published as a single note 🤯🤯🤯 The possibilities are endless nostr:nevent1qvzqqqqqqypzqrtvswydevzfhrw5ljxnmrpmhy778k5sh2pguncfezks7dry3z3nqythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qqsrg2e30zw7m8a2vqjusdlv90rt983ynju6hel045lymyu3zdj6necxlykfe

Next week we will launch the new ContextVM website 🚀🚀 Stay tunned

ContextVM lets anyone run and use Model Context Protocol (MCP) servers over Nostr. In practice, that means MCP clients can connect to MCP servers through Nostr relays—securely, without central gatekeepers, from any device with an internet connection. Think of it as a thin, elegant transport layer: we don’t replace MCP; we free it. By moving identity, discovery, connectivity, and payments into a decentralized fabric, ContextVM makes MCP truly permissionless and globally accessible.

Thank you, nostr:npub1mgvwnpsqgrem7jfcwm7pdvdfz2h95mm04r23t8pau2uzxwsdnpgs0gpdjc for sharing this article. We are honored that the work we are doing with ContextVM is inspiring others in the ecosystem. 🦾 nostr:naddr1qvzqqqr4gupzpkscaxrqqs8nhaynsahuz6c6jy4wtfhkl2x4zkwrmc4cyvaqmxz3qyghwumn8ghj7mn0wd68ytnhd9hx2tcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uqq6vfhx56rqv3s8quryvfexssnnrme

Proposal for ContextVM Payments We're enhancing the payment system for ContextVM and its TypeScript SDK to create a flexible and robust framework that supports multiple payment methods like Bitcoin, Lightning, Cashu, and we are looking for some feedback. Here’s our current progress: We propose introducing a `payment_method` field to clearly identify the payment method used in payment request notifications, aligning with the W3C Payment Method Identifiers (PMI) specification. This ensures interoperability and future-proofing, making it easier to support various currencies and payment systems. Payment identifiers will look like `bitcoin-lightning`, `bitcoin-lightning-bolt11`, or `ecash-cashu`. On the SDK side, we propose a modular architecture with `PaymentHandler` and `PaymentProcessor` interfaces for client and server transports, respectively. This approach allows different payment methods to coexist seamlessly, enabling users to implement their own payment methods by adhering to these interfaces. However, we face some challenges. One main hurdle is handling mismatching payment methods between clients and servers effectively. To address this, we propose maintaining an array of payment handlers or processors, each satisfying a standard interface and specific to a payment method. For example, a server supporting both Lightning Network (LN) and Cashu would be initialized with [LNPaymentProcessor, CashuPaymentProcessor], while a client supporting only LN would be initialized with just [LNPaymentHandler]. More info in the linked issue below We invite you to review our progress and provide valuable feedback: ContextVM Spec PR: https://github.com/ContextVM/contextvm-docs/pull/2 ContextVM ts-sdk: https://github.com/ContextVM/ts-sdk/issues/6 Your insights and suggestions are crucial in helping us overcome these challenges and shape these updates. Let's build a better payment system together!

Thank you to everyone who joined the call today! It was a great conversation. We covered: - Spec overview - SDK overview - A demo of a traditional MCP host client communicating with an MCP server over Nostr - A discussion about possible use cases. - Discussion about Paid MCP - Q&A

Well, well! Today we will be celebrating our first community call. If you are interested in ContextVM, MCP, Nostr, Bitcoin, or any related topics, join the conversation. - When? 16:00 UTC - What? An introduction to the spec, current tooling, next steps, and questions and discussions about other topics. - Where? HiveTalk https://honey.hivetalk.org/dashboard/event/naddr1qvzqqqrkdypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqyv8wumn8ghj7un9d3shjtngd9mx2arpd34jummjvuqq5arvd4ck6vr5xpnkspjhzu3

New version of the TypeScript SDK v0.1.12 This release includes a reconnection mechanism with exponential backoff, removal of direct access to the private key in the 'privateKeySigner', structured logging, handling of ill-formed or invalid JSON, and improvements to the reconnection logic with resubscription. These enhancements make the SDK more robust. Changelog: - ee82a52: feat: improve relay reconnection handling with subscription persistence - eecd6af: fix: handle malformed json content in nostr events gracefully - dd8f444: feat: implement structured logging system with configurable levels - c18f47c: refactor: nostr signer with nip44 encryption and remove direct secret key access - 636b197: chore: bump deps - d5fd1a8: feat: add message validation and relay reconnection with exponential backoff

"Today, Big Tech is repeating the mistakes from the internet’s early days. Instead of using AI to serve people, they’re turning people into products — and using AI to accelerate the surveillance-capitalism business model built on advertising, data harvesting, and exploitation." https://proton.me/blog/lumo-ai Yes, we couldn't agree more! nostr:naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqyt8wumn8ghj7un9d3shjtnwdaehgu3wdejhgtcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcqzenx7un8d9hxwttp94hx2aedveex7mn5d9jhys0cfsc

We just wrote an article explaining why we are working on ContextVM. We are just starting, and our first communications were directed to developers. However, we thought it was important to share what motivates us. nostr:naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqyt8wumn8ghj7un9d3shjtnwdaehgu3wdejhgtcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcqzenx7un8d9hxwttp94hx2aedveex7mn5d9jhys0cfsc

This CLI programs enables you to use ContextVM with any existing MCP client or server. The proxy enables you to access MCP via Nostr using any client, including Claude Desktop/Code, Goose, Cursor, and others. The gateway allows you to expose any existing MCP server through Nostr, reducing the barrier between ContextVM and any MCP system. The CLIs are multiplatform and run on Linux, Windows, and macOS. nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqqsqz0v744kkaaamrp59dwqjlgf67smk3mj075jewdgk8tyn5z09ghgrnr2l0

We plan to release some demo videos tomorrow. Stay tuned! 🚀 nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqzqqfan6kk6mhhhvvxs44cztap8t6rw68wfl6jt9e4zcavjwsfu4zaaajuzu

Exciting Updates from ContextVM: Introducing Gateway CLI and Proxy CLI We are thrilled to announce the latest developments in the ContextVM project! Following our rebranding from DVMCP to ContextVM, we continue to deliver innovative solutions to enhance the integration of MCP systems with the Nostr network. Today, we are excited to introduce two new command-line interface (CLI) tools: `gateway-cli` and `proxy-cli`. ## Gateway-CLI and Proxy-CLI They use the `NostrMCPGateway` and `NostrMCPProxy` which are internal components of the ContextVM/ts-sdk, designed to bridge traditional MCP systems with the Nostr network. Here’s a brief overview of each: - **NostrMCPGateway**: This server-side component exposes a traditional MCP server to the Nostr network, acting as a gateway that translates communication between Nostr-based clients and a standard MCP server. For more detailed information, visit the https://www.contextvm.org/gateway/overview/ - **NostrMCPProxy**: This client-side component acts as a local proxy, exposing a mcp server locally, and translating communication between a standard MCP client and a remote, Nostr-based MCP server. For more detailed information, visit the https://www.contextvm.org/proxy/overview/ ### Gateway CLI The `gateway-cli` is a tool designed to simplify the deployment and configuration of the `NostrMCPGateway`. It allows you to expose your MCP server through the Nostr network with ease. **Quick Start Installation:** ```bash curl -fsSL https://raw.githubusercontent.com/contextvm/gateway-cli/main/install.sh | bash ``` **Alternative Installation Methods:** - **From Binaries**: Download the latest release from the https://github.com/contextvm/gateway-cli/releases and follow the instructions. - **With Deno**: Run `deno run -A jsr:@contextvm/gateway-cli` or install it with `deno install -A gateway-cli jsr:@contextvm/gateway-cli`. **Example Usage:** ```bash gateway-cli --private-key "your_private_key" --relays "wss://relay.com" --server "command arg1 arg2" ``` For more detailed information, including configuration options and development instructions, visit https://github.com/ContextVM/gateway-cli. #### Proxy CLI The `proxy-cli` is designed to wrap around the `@contextvm/ts-sdk`'s `NostrMCPProxy`, allowing you to connect to MCP servers exposed through the Nostr network and use them as local MCP servers in any MCP client. Allowing any MCP client to support nostr transport, even if it doesn't supports it natively **Quick Start Installation:** ```bash curl -fsSL https://raw.githubusercontent.com/contextvm/proxy-cli/main/install.sh | bash ``` **Alternative Installation Methods:** - **From Binaries**: Download the latest release from the https://github.com/contextvm/proxy-cli/releases and follow the instructions. - **With Deno**: Run `deno run -A jsr:@contextvm/proxy-cli` or install it with `deno install -A jsr:@contextvm/proxy-cli`. **Example Usage:** ```bash proxy-cli --private-key "your_private_key" --relays "wss://relay.com" --server-pubkey "server_public_key" ``` For more detailed information about the CLIs, including configuration options and development instructions, visit the https://github.com/ContextVM/proxy-cli For more information about ContextVM, visit http://contextvm.org If you have any doubt don't hesitate to ask

We also have a signal group for the community https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7un9d3shjtnwdaehgu3wdejhgtcqyp0fs5ztdyvyajflvka3yqpqg9k60fym4f0fjlxpddflhjuxcmm866a3sze

GM Nostr! We will be hosting a community call on July 25th at 16:00 UTC. 🚀 During this call, we will walk through the new overhaul and discuss the architecture of ContextVM. There will also be space to chat about related topics, ask questions, clear doubts, share use cases, and discuss adjacent topics. Our goal is to create a regular space for discussing ContextVM and related topics such as MCP, AI, Nostr, and Bitcoin. Whether you already understand what ContextVM is or not, please join us and don't be afraid to ask questions. https://honey.hivetalk.org/dashboard/event/naddr1qvzqqqrkdypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqyv8wumn8ghj7un9d3shjtngd9mx2arpd34jummjvuqq5arvd4ck6vr5xpnkspjhzu3

To clarify, there was a typo in our previous message 🙏 We meant July instead of October for the community call. We are eager to host a community call on either July 24 or 25, next week. These dates are not set in stone yet. We want to know if these dates work for you so we can determine the final date. If you want to participate, please share your preference. nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqyf8wumn8ghj7u3wv3mx6cms9en82m30qy88wumn8ghj7mn0wvhxcmmv9uqzp75ye55tak9tnzdmry84tkmej3jtldp06j77uqer222qr3hmz7kk62rdyp

Thanks to nostr:npub1aljazgxlpnpfp7n5sunlk3dvfp72456x6nezjw4sd850q879rxqsthg9jp for the contribution, the contextvm.org page now has an llms.txt file! You can find it at the following URL: https://contextvm.org/llms.txt This makes it pretty easy to start working with ContextVM using LLMS.