Provides MCP-enabled data access through Nostr’s DVM network for discovering and executing tools.
Configuration
View docs{
"mcpServers": {
"gzuuus-dvmcp": {
"command": "bunx",
"args": [
"dvmcp-bridge"
]
}
}
}You connect MCP servers to Nostr’s Data Vending Machine ecosystem using DVMCP, enabling discovery, access, and execution of AI and computational services in a decentralized, verifiable way. This bridge approach combines MCP’s capability framework with Nostr’s secure messaging to streamline MCP service usage without centralized registries.
You use MCP clients to discover and invoke tools exposed by DVMCP-enabled servers. With the bridge running, your MCP client can discover available tools, send requests, and receive results through the decentralized DVM network. Messages are cryptographically signed, ensuring authenticity and integrity, while the system remains resilient to single points of failure.
Prerequisites you need before starting are simple: ensure Bun is installed on your system. Bun is used to run the DVMCP bridge and discovery services directly without a full installation.
# Quick start with Bunx (no installation required for the commands shown)
bunx dvmcp-bridge
bunx dvmcp-discovery
# Global installation (optional, to run commands directly)
bun install -g @dvmcp/bridge @dvmcp/discovery
dvmcp-bridge
dvmcp-discoveryIf you prefer to run the MCP components via a local setup, you can start the bridge and the discovery service using Bunx as shown above. If you have installed the packages globally, you can start the services with the plain command names dvmcp-bridge and dvmcp-discovery. These utilities expose the MCP-enabled bridge and discovery endpoints that your MCP client will interact with through the Nostr-based DVM network.
Bridge that connects MCP servers to Nostr's DVM ecosystem, handling tool announcements, execution, and status updates.
Discovery service that aggregates MCP tools from DVMs and makes their tools available to clients.