dvmcp

DVMCP is a bridge between MCP servers and Nostr's Data Vending Machine (DVM) ecosystem. It enables MCP-powered tools and capabilities to be discovered, requested, and executed via decentralized Nostr messages, using JSON-RPC style interactions. The discovery service aggregates tools declared by MCP servers and exposes them over the DVMCP protocol so clients on Nostr networks can discover what services are available, understand their capabilities, and invoke them in a verifiable, cryptographically signed manner. This makes MCP-based AI or computation services accessible without centralized registries while preserving interoperability with Nostr event kinds and data exchange flows.

To use it, run the DVMCP discovery service (and the bridge when needed). The bridge publishes tool announcements and status updates to DVMs, while the discovery service collects MCP tools from participating servers and makes them available to DVMs. Clients can query the tools list, resources, prompts, and tool capabilities, then submit requests and receive responses through the DVM workflow, all in a decentralized manner.

Prerequisites:

• A supported runtime (Node.js/Bun as used in this project).
• Git to clone the repository.

1. Clone the repository: git clone https://github.com/gzuuus/dvmcp.git cd dvmcp

2. Install dependencies (using Bun as described in the repository): bun install

3. Run the discovery service and bridge (quick start): bunx dvmcp-discovery bunx dvmcp-bridge

If you prefer a global style setup (per the project's quick start):

4. Global installation ( Bun-based): bun install -g @dvmcp/bridge @dvmcp/discovery

5. Run the commands directly: dvmcp-bridge dvmcp-discovery

Note: The project is archived and superseded by ContextVM/sdk, so consider upgrading to the newer ContextVM tooling for production use. The commands above reflect the repository’s Quick Start as provided in the README.

Tips and considerations:

• The project is archived and superseded by ContextVM/sdk; for production workloads, prefer the modern SDKs and tooling from that project.
• Prerequisite tool: Bun must be installed for the quick-start commands (bunx, bun, etc.).
• The DVMCP workflow relies on Nostr event kinds for server announcements, tool lists, resources, prompts, and request/response messages; ensure your DVM client can sign and verify these messages.
• Environment variables (as placeholders) can be used to configure logging, config paths, and operational modes. Customize as needed for your deployment.
• If you run into issues, check that the discovery and bridge services are accessible and that their published tool metadata (tools list, resources, prompts) are synchronized.
• This MCP server set supports decentralized discovery and cryptographic verification, but always validate tool configurations and authorization in your specific DVM/network context.