This should be fixed now 🫡 As a side effect, we forked Strfry to add a convenient way to deploy a relay and some write policies to harden it for CVM usage.

GitHub

GitHub - ContextVM-org/strfry-cvm: a nostr relay

a nostr relay. Contribute to ContextVM-org/strfry-cvm development by creating an account on GitHub.

View quoted note →

Spam attack in our relays. Fixing now

A simple, but powerful concept View article →

Use it from contextvm.org or through the CVMI CLI. 1. Configure an alias for easy calling: `npx cvmi config add ots @npub1u8qu...segw` 2. OTS an event: `npx cvmi call ots ots_event target=<event-id‑nevent‑naddr>` 3. Verify the attestation and get its state: `npx cvmi call ots verify_ots target=<event-id‑nevent‑naddr>` If you want, you can configure it as an MCP in your preferred agentic framework; just set `npx cvmi use @npub1u8qu...segw` in your MCP configuration. View quoted note →

🕰 New public server available! 🕰 This is an OTS client that lets you easily Open Time Stamp any Nostr event. The usage is straightforward: two tools, 'ots_event' to create an attestation for an event, and 'verify_ots', which lets you verify the OTS attestation and its state in the time chain. With this server, you or your agents can easily OTS any Nostr event. Here’s a brief demo: The project’s code is open source, and you can run your own instance if you wish. By default it uses public Bitcoin nodes to verify the attestations, so you don’t need to run your own node.

GitHub

GitHub - ContextVM-org/ots-cvm

Contribute to ContextVM-org/ots-cvm development by creating an account on GitHub.

Server page: https://www.contextvm.org/s/e1c1c32729cbd542c9b9ce7ee6e421c434e07835228020c4f57140782f02496a You can use this service for free, but public OTS servers need to cover operating costs. If you’d like to donate, please refer to opentimestamps.org.

🌍 New issue of the ContextVM world newsletter 🌍 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 for clients to discover them. We also discuss new CVMI capabilities and other news from the ecosystem, plus demos and a new Rust SDK that is currently being built. Hope you enjoy it! Don’t miss any issue, subscribe 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 →

Make your MCPs over Nostr, composable, token efficient, easy 🚀 View article → #mcp

The cool part about the demo, ahead of the reduction in token usage compared to building this with the MCP interface, is the progressive disclosure. The LLM didn’t know anything about Earthly, Wolfram, or Relatr, and it discovered tools and usage as needed. No extra tool schemas were loaded unnecessarily, no bloated context window, just organic discovery and usage. View quoted note →

We’re thrilled to roll out CVMI CLI 0.2.x, adding two powerful commands: `call` and `discover`. `call` lets you invoke CVM servers straight from the command line, perfect for debugging or plugging into agents. No MCP config or schema loading needed; responses are cleaned to save tokens. Save servers with aliases and run them like `npx cvmi call relatr`. `discover` query relay announcements to list available tools, just run `npx cvmi discover`. Demo: query Earthly and Wolfram for the Eiffel Tower’s address and height Get Sovereign Engineering pubkey using Relatr. These upgrades make CVM servers far easier to use and compose, cut token costs versus MCP, and give developers a simple way to debug, script, or integrate CVM services from the command line. Some screenshots of this new capabilities:

🚀 CEP-17 is now merged into ContextVM, and it is available in the ts SDK from v0.7.x.

ContextVM Documentation

CEP-17 Server Relay List Metadata

Relay list publication mechanism for ContextVM servers using NIP-65 conventions

This is a meaningful step forward for resilience. With CEP-17, servers can publish the relay list they use following NIP-65, and clients can resolve connection paths more intelligently: first from explicit configuration, then from relay hints embedded in `nprofile`, and then if nothing is define from relay list discovery. That makes connectivity more robust by default, reduces dependence on central points of failure, and avoids hardcoded relays in normal client setup. It also makes client configuration simpler. In many cases, you can now just pass an `nprofile` string and clients will use its relay hints directly; if those are not available, it can fall back to CEP-17 discovery through NIP-65 relay-list metadata. The reference implementation is already in the SDK, the docs and skills have been updated, and contextvm.org now surfaces these new `nprofile` identifiers as well. Small change in surface, big improvement in how reliably clients can find and reach servers across a more sovereign network 🚀

We’re so back. DNS problems have been resolved, sites and relays are reachable again 🚀 View quoted note →

We've been having problems with DNS and registrars, which is why our ContextVM websites are down. We have a pending transfer that should be resolved soon. In the meantime, we’ve deployed the main site and documentation on GitHub Pages as a backup alternative. The links are: - https://contextvm.github.io/contextvm-site/ -

ContextVM Documentation

ContextVM

The intersection of Nostr and MCP

Sorry for the inconvenience. CVM servers are still running, and clients can still connect using any relay, there’s no disruption there 🦾

Nostr == WS == CVM. Connecting to servers, calling tools, etc, everything has worked over WebSockets since day one with ContextVM 🚀 View quoted note →

A new issue of our biweekly newsletter is out! 🚀 "Ephemeral Is Better — The ContextVM World #3" Available in nostr and substack:

Ephemeral Is Better — The ContextVM World #3 🌍

GM people, and welcome to the third issue of “The ContextVM World”, your biweekly appointment to discover everything you need to know about Con...

View article →

Continuing with NIPs, we have just added a pr for CVM to the NIPs repository. We wrote this NIP to describe the conventions for transporting Model Context Protocol (MCP) messages over Nostr. We deliberately kept the NIP thin on details that already live in the full CVM spec; it exists to make CVM discoverable in the Nostr ecosystem and to show that CVM is just Nostr, using the same primitives any Nostr app uses.

GitHub

NIP-XX: ContextVM, MCP JSON-RPC over Nostr by ContextVM-org · Pull Request #2246 · nostr-protocol/nips

I wrote this NIP to describe ContextVM (CVM): a minimal convention for transporting Model Context Protocol (MCP) JSON-RPC messages over Nostr. The ...

We just opened a PR in the NIPs repo that includes this convention for ephemeral gift wraps. Perhaps other developers will find it a valuable building block

GitHub

NIP-59: Add ephemeral gift wrap event kind (21059) by ContextVM-org · Pull Request #2245 · nostr-protocol/nips

Adds support for ephemeral gift wraps (kind:21059) following the same semantics as regular gift wraps (kind:1059) but with ephemeral event semantic...

View quoted note →

Ephemeral giftwraps improve your privacy and hygiene on relays, as nothing is persisted there. CVM messages use ephemeral events when the traffic is not encrypted, but when encrypted, they wrap the ephemeral events in a gift wrap which uses a regular kind. So even if the wrapped event is ephemeral, its envelope isn't. Ephemeral gift wraps solve this; everything is encrypted end-to-end, relays just route blindly, nothing is persisted, no collect now, decrypt later 🥷🏼 View quoted note →

CEP-19 is live with ephemeral gift wraps 🚀 In plain terms, you can now send end-to-end encrypted MCP messages that do not have to be stored on relays. This is a significant upgrade for privacy, as your messages can travel through public infrastructure without becoming permanent data. The kind used by CVM is ephemeral (25910), and when you use encryption, this ephemeral kind is gift-wrapped (NIP-59) in a regular event kind that is persistent on relays (1059). With this update, servers and clients can use a new kind for ephemeral gift wraps (21059). It is exactly the same as the regular kind (1059) but is ephemeral, so it is not stored on relays. This also improves metadata hygiene: relays can forward messages without needing to retain payloads. How it works: CEP-19 introduces an ephemeral gift-wrap kind alongside the existing persistent kind. Both sides advertise their support, and when both do, the transport prefers ephemeral wrapping while maintaining backward compatibility with older clients. Configuration in the SDK: This feature is available from version v0.6.0. Just set the transport’s `GiftWrapMode` option to `EPHEMERAL` to always use ephemeral gift wraps, `PERSISTENT` to force legacy behavior, or `OPTIONAL` to negotiate ephemeral wrapping when supported. The default remains compatible with existing relays and clients, making this an opt-in privacy upgrade without being a breaking change.

Hey Nostr! We're excited to share that we're working on getting more eyes on ContextVM and its development. We just published our first post on Hacker News. If you're on the platform, we'd love for you to check it out, share your thoughts, or help spread the word. Every bit helps, so please join us in growing ContextVM! 🚀

Show HN: ContextVM – Running MCP over Nostr | Hacker News

Now that payments are in place, we are going to work on: - CEP-19 for ephemeral gift wraps:

GitHub

Issues · ContextVM/contextvm-docs

ContextVM documentation and specification. Alternative link: https://contextvm.github.io/contextvm-docs/ - Issues · ContextVM/contextvm-docs

and - CEP-17 for servers relay list:

GitHub

Issues · ContextVM/contextvm-docs

ContextVM documentation and specification. Alternative link: https://contextvm.github.io/contextvm-docs/ - Issues · ContextVM/contextvm-docs

Both CEPs are quite minimal but yet beneficial for the ecosystem. CEP-19 provides better privacy guarantees, as servers and clients will be able to use ephemeral gift wraps for encrypted communications. Currently, they use regular gift wraps, which are regular events, and even if the events inside are ephemeral, they are wrapped in a regular envelope. CEP-17 defines how servers can announce relay lists (NIP-65) to improve discoverability. Simple but powerful! LG!🚀 After this iteration we will come back to CEP-15 introducing common tool schemas, which is a bigger one

GitHub

[CEP-15] Common Tool Schemas · Issue #15 · ContextVM/contextvm-docs

Preamble Title: Common Tool Schemas Authors: ContextVM-org Status: Draft Abstract This CEP establishes a standard for defining and discovering comm...