mcpField
🌐
🌐 Decentralized MCP Registry

🌐 Decentralized MCP Registry

Local
github.com/o2alexanderfedinDeveloper Tools1Updated 62w ago
Repository

About 🌐 Decentralized MCP Registry

Decentralized MCP Registry is a peer-to-peer registry concept for discovering and delegating tools across MCP servers without a central control point. It is in early development, with work focused on connectivity, metadata, discovery, and relay functions.

Key features

  1. 01Peer-to-peer registry architecture
  2. 02Unified server and tool catalog
  3. 03Remote tool invocation relay
  4. 04Multiple tool versions and dependencies
  5. 05Cryptographic verification and web of trust
  6. 06Micro-billing framework

Use cases

  1. 01Discover tools across peer MCP servers
  2. 02Relay tool calls between network participants
  3. 03Manage tool versions and dependencies
  4. 04Verify server trust in a decentralized network

MCP support

Designed to connect MCP servers in a peer-to-peer registry, with tool discovery, a composite catalog, and relayed tool invocation. The project is in initial development.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

🌐 Decentralized MCP Registry

A peer-to-peer (P2P) registry system for Model Control Protocol (MCP) servers, inspired by BitTorrent protocols. This decentralized solution enables seamless tool discovery and delegation without central points of failure or control.

🚀 Features

  • Decentralized Architecture: Fully P2P network without central points of control
  • Tool Discovery: Unified MCP server interface with composite tools catalog
  • Direct Tool Invocation: Seamless relay of tool invocations across the network
  • Version Management: Support for multiple tool versions and dependencies
  • Security & Trust: Cryptographic verification and web of trust model
  • Monetization: Built-in micro-billing framework with mutual clearing capabilities

📋 Requirements

See Requirements Document for detailed specifications.

🛠️ Development Status

Currently in initial development phase, focusing on:

  • Basic P2P connectivity
  • Simple tool registry with metadata
  • Core relay functionality
  • Basic tool discovery
  • Cryptographic verification
  • Local tool execution support

📝 License

This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). See the LICENSE file for details.

Commercial Licensing

This software is also available under a commercial license. For commercial use, modification, or distribution of this software, please contact the copyright holder to discuss commercial licensing options.

🤝 Contributing

Contributions are welcome! Please read our Contributor License Agreement before submitting pull requests.

📚 Documentation

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.