MCP.so
登录

Decentralized MCP Registry

@o2alexanderfedin

基本信息

分类

其他

许可证

View license

传输方式

stdio

作者

o2alexanderfedin

关于 Decentralized MCP Registry

A decentralized P2P registry for MCP servers using BitTorrent-inspired protocols. Enables seamless tool discovery and delegation without central points of failure.

Decentralized MCP Registry 配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块,请前往代码仓库查看安装说明。

代码仓库

Decentralized MCP Registry 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Decentralized MCP Registry?

It is a peer-to-peer (P2P) registry system for Model Control Protocol (MCP) servers, inspired by BitTorrent protocols. Designed for developers, it enables seamless tool discovery and delegation without central points of failure or control.

How to use Decentralized MCP Registry?

The project is in its initial development phase; no installation or configuration instructions are currently available. Developers should refer to the Requirements Document for detailed specifications and planned functionality.

Key features of Decentralized MCP Registry

  • Decentralized P2P architecture without central control
  • Unified MCP interface for composite tool discovery
  • Direct relay of tool invocations across the network
  • Support for multiple tool versions and dependencies
  • Cryptographic verification and web of trust model
  • Built-in micro-billing framework with mutual clearing

Use cases of Decentralized MCP Registry

  • Discovering MCP tools from a P2P network of registries
  • Delegating tool invocations to remote peers without central servers
  • Managing multiple versions and dependencies of MCP tools
  • Verifying tool authenticity and trust via cryptographic proofs
  • Enabling micro-transactions for tool usage through a billing framework

常见问题

1

What is the current development status?

The project is in the initial development phase, focusing on basic P2P connectivity, simple tool registry, core relay, tool discovery, cryptographic verification, and local tool execution support.

2

What are the runtime requirements or dependencies?

Specific runtime requirements or dependencies are not listed in the README. Detailed specifications can be found in the Requirements Document.

3

What license is this project under?

It is licensed under AGPL-3.0, with a commercial license available upon request for non-AGPL use.

4

How can I contribute to the project?

Contributions are welcome. Review the Contributor License Agreement before submitting pull requests.

5

Where is the full documentation?

Currently, only the Requirements Document is available. API documentation and a development guide are marked as “coming soon.”

评论

其他 分类下的更多 MCP 服务器