Cowrie Research

contextvm

3 min read

ContextVM

  • Name: ContextVM
  • URL: https://www.contextvm.org/
  • Category: MCP-over-Nostr transport infrastructure / decentralized AI-tool and remote-service fabric / optional Bitcoin-micropayments layer
  • Tags: bitcoin-ecosystem
  • Summary: ContextVM is Nostr transport for MCP servers, not an AI app. The useful thing is simple: discovery, encrypted transport, and optional paid access move onto keys and relays instead of domains, OAuth, or port forwarding.
  • What it does:
    • Runs MCP transport over the Nostr network so remote servers can be reached without conventional web-hosting primitives
    • Provides JavaScript/TypeScript SDK components for Nostr client/server transports, relay handling, signing, gateway, and proxy patterns
    • Lets existing MCP servers gain Nostr interoperability without abandoning their conventional transports
    • Supports both public servers announced to relays and private servers accessed directly by known public key
    • Exposes a public server-discovery surface for ContextVM-enabled MCP services
    • Supports optional paid service access through Bitcoin/Lightning-style micropayment flows
  • Key claims:
    • The homepage describes ContextVM as a transport layer for MCP over the Nostr network and emphasizes “no domains, no OAuth, no port forwarding—just keys, relays, and optional payments”
    • The homepage says ContextVM works with any MCP server and explicitly frames the Gateway/Proxy approach as a way to extend existing MCP servers and clients rather than forcing a rewrite
    • The homepage also presents direct value exchange as a core feature, saying providers can monetize with Bitcoin micropayments and other payment methods without intermediaries
    • The About page says ContextVM “liberates” MCP by running it over Nostr and moving identity, discovery, connectivity, and payments into a decentralized fabric
    • The About page says the project supports both public and private servers, preserving portable identity, outbound-only connectivity, and optional payments in either model
    • The FAQ says Nostr provides discovery through service announcements, transport through signed and encrypted Nostr events, and optional payments using Bitcoin and the Lightning Network
    • The SDK README says the ContextVM Protocol uses Nostr plus Model Context Machines to expose MCP server capabilities through a decentralized, cryptographically secure messaging system
    • The SDK README says the package includes Nostr client/server transports, a Proxy, a Gateway, relay management, and signing primitives so existing MCP servers can gain Nostr interoperability
  • Whitepaper: No canonical standalone ContextVM whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official homepage, about and FAQ pages, public servers page, the SDK README/package metadata, and the public GitHub organization; see ../whitepapers/contextvm-primary-sources-2026-05-02.md.
  • Sources:

Internal linkages

Graph View