Colber

Name: Colber
Author: Obi49

@Obi49

リポジトリ

Colber について

概要はまだありません

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

Obi49

投稿者

Obi49

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "colber": {
      "command": "npx",
      "args": [
        "-y",
        "@colber/mcp"
      ],
      "env": {
        "COLBER_BASE_URLS": "{\"identity\":\"https://api.colber.dev/identity\",\"reputation\":\"https://api.colber.dev/reputation\",\"memory\":\"https://api.colber.dev/memory\",\"observability\":\"https://api.colber.dev/observability\",\"negotiation\":\"https://api.colber.dev/negotiation\",\"insurance\":\"https://api.colber.dev/insurance\"}"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Colber?

Colber is an infrastructure layer of trust, coordination, and continuity for the agent economy. It provides five integrated services—Reputation, Memory, Observability, Negotiation, and Insurance—exposed through SDKs (TypeScript, Python) and the Model Context Protocol (MCP).

How to use Colber?

Install the SDK via npm (@colber/sdk) or pip (colber-sdk), then create a ColberClient pointing to https://api.colber.dev. For MCP integration, add @colber/mcp as a server in your MCP client config (e.g., Claude Desktop) using npx -y @colber/mcp. All capabilities are then accessible programmatically or as 27 MCP tools.

Key features of Colber

Cryptographic reputation with offline-verifiable attestations (Ed25519 + JCS)
Persistent semantic memory with vector search and ACLs
Distributed A2A tracing and logging via ClickHouse (OpenTelemetry-compatible)
Multi-party negotiation with auctions, multi-criteria, and signed settlement
Deliverable insurance with reputation-based pricing, escrow, and arbitration
Full open-core surface (SDKs, MCP server, types) under Apache-2.0

Use cases of Colber

An AI agent verifying another agent’s reputation before a transaction
Storing and retrieving agent-specific memory with vector search
Debugging multi-agent workflows with distributed observability
Negotiating resource allocation or task delegation among multiple agents
Insuring agent deliverables against non‑performance

FAQ from Colber

What is Colber for, and how does it differ from other agent tools?

Colber is the infrastructure for trust, coordination, and continuity across agents—not a single-purpose tool. It bundles five integrated modules (Reputation, Memory, Observability, Negotiation, Insurance) behind one SDK/MCP interface, providing a full lifecycle for agent-to-agent interactions.

What dependencies or runtime does Colber require?

Using the SDKs only requires a JavaScript (Node.js 18+/Deno/Bun) or Python (3.8+) runtime. The MCP server needs Node.js 22+. The hosted platform runs on colber.dev and is accessed via HTTPS; there is no self‑hosting of the backend.

Where does agent data live?

All data processed by the Colber modules (reputation scores, memory entries, traces, negotiations, insurance contracts) lives on the Colber hosted platform (api.colber.dev). The open‑core SDKs and MCP server are client‑side only and never store data.

What transports and authentication are supported?

The SDKs communicate over HTTPS (REST/gRPC). The MCP server supports stdio (default) and HTTP transport with configurable port. Authentication tokens can be passed via environment variables or config; details are in apps/mcp-server/README.md.

Are there any known limits on the open-core version?

The open‑core repo (this one) contains only client‑side code (SDKs, MCP server, types). The server‑side implementation of the five modules is proprietary and operated solely on colber.dev. There is no limit on the number of agents or requests, but usage is subject to Colber’s Terms of Service.