DVMCP: Data Vending Machine Context Protocol

Created By
gzuuusa year ago
DVMCP is a bridge implementation that connects Model Context Protocol (MCP) servers to Nostr's Data Vending Machine (DVM) ecosystem
Overview

What is DVMCP?

DVMCP (Data Vending Machine Context Protocol) is a bridge implementation that connects Model Context Protocol (MCP) servers to Nostr's Data Vending Machine (DVM) ecosystem, enabling AI and computational tools to be discovered and utilized via Nostr's decentralized network.

How to use DVMCP?

To use DVMCP, you can run the packages directly using npx without installation or install them globally using npm. The interactive CLI will guide you through the configuration setup on the first run.

Key features of DVMCP?

  • Connects MCP servers to Nostr's DVM ecosystem.
  • Provides a discovery service for aggregating MCP tools from DVMs.
  • Offers shared utilities and components across DVMCP packages.

Use cases of DVMCP?

  1. Bridging AI tools with decentralized networks.
  2. Aggregating and discovering computational tools in a decentralized manner.
  3. Facilitating communication between MCP servers and DVMs.

FAQ from DVMCP?

  • What is the prerequisite for using DVMCP?

Ensure you have Bun installed.

  • Can I run DVMCP without installing it?

Yes! You can use npx to run the packages directly.

  • How do I set up a bridge?

Follow the interactive setup after running npx @dvmcp/bridge to configure your MCP server path and Nostr private key.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gzuuus
Star
23
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago