Bee: Quantum Intelligence

io.github.heossihq由 GitHub 帳號 heossihq 發布v1.0.98更新於 Nov 3, 2026

Bee governed intelligence for chat, code, research, documents, and memory.

已驗證Streamable HTTP可網頁執行知識與記憶AI 與機器學習

概覽

AI 產生的概覽

Bee 的 MCP 伺服器讓助理接入 HEOSSI 的託管多模態智慧平台,用於對話、程式碼、研究、文件與記憶。

可以做什麼
  • 透過相容於 OpenAI 的閘道向 Bee 託管模型送出對話與補全請求
  • 在受治理的平台上處理程式碼、研究、文件與記憶相關任務
  • 依 API 金鑰所屬方案選擇 bee-cell 至 bee-swarm 的模型層級
  • 可作為遠端端點使用,也可用 uvx 從 bee-sdk 套件在本機啟動程序
適用情境
當你希望助理把任務交給 Bee 的託管模型與受治理平台、而非單一本機模型時適合加入;也可用免費的 Cell 層級先行試用。
執行需求
需要 Bee API 金鑰(bee_sk_...)填入 BEE_API_KEY,或透過 Authorization 標頭使用 OAuth;金鑰可在 Bee Workspace 建立,免費 Cell 層級即可使用。需能連線至 Bee 閘道。可選 BEE_API_URL 指定 Enclave 或預備環境閘道,BEE_MODEL 指定預設層級。本機方式需 uv/uvx 與 bee-sdk 套件。
安裝前請注意
API 金鑰是敏感憑證,以 bearer 形式傳送,請勿寫入共用設定。請求與內容會送往 HEOSSI 的託管閘道這個第三方服務。用量可能依方案計量或受限,較高模型層級取決於金鑰權限。模型引擎與閘道為專有實作,行為僅由公開契約定義。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Bee: Quantum Intelligence,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.heossihq%2Fbee-public/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "bee-quantum-intelligence": {
      "type": "http",
      "url": "https://api.bee.heossi.com/mcp"
    }
  }
}

README

[Bee: Quantum Intelligence]

Bee: Quantum Intelligence™

[npm] [PyPI] [MCP Registry] [License]

Website | Documentation | Packages | Machine-readable package index | System status

The public developer distribution for Bee, HEOSSI's governed multimodal intelligence platform. This repository contains the actual source of Bee's Apache-2.0 SDKs, MCP integration, API contracts, runnable examples, and public trust-verification material.

This repository is generated from reviewed, public-safe paths in the Bee monorepo. MANIFEST.json records the exact source commit and content digest for every export; SHA256SUMS and the SPDX SBOM support independent artifact inspection.

Developer surface

The canonical package catalog records each public developer distribution, exact version, registry, role, license boundary, and install command. Its machine-readable companion is PACKAGE-INDEX.json. These distributions do not expose the private Bee service monorepo.

SurfaceInstall or entry pointSource / contract
TypeScript SDKnpm install @heossihq/beesdks/typescript
Python SDKpip install bee-sdksdks/python
MCP serveruvx --from bee-sdk@latest bee-mcpmcp · server.json
OpenAI-compatible APIhttps://api.bee.heossi.com/beeopenapi.json · postman.json
Bee: Quantum Intelligence - CodeHeossi.beecodeMicrosoft Marketplace · Open VSX
Bee Code CLInpm install -g @heossihq/beecodeDownload guide
PQ assuranceSigned public coverage registertrust/pq-register

Quickstart

ts
import { BeeClient } from "@heossihq/bee";
const bee = new BeeClient({ apiKey: process.env.BEE_API_KEY! });const result = await bee.chat.completions.create({  model: "bee-cell",  messages: [{ role: "user", content: "Explain hybrid post-quantum TLS." }],});
console.log(result.choices[0].message.content);

Create an API key in Bee Workspace. The free Cell tier works with both SDKs and MCP.

Repository map

text
api/                 Versioned OpenAPI and Postman contractsdocs/                Public architecture and enterprise scenario flowsexamples/            Runnable TypeScript and Python examplesmcp/                 Client configuration and MCP setupsdks/typescript/     Published @heossihq/bee package source and testssdks/python/         Published bee-sdk and bee-mcp source and teststrust/pq-register/   Public PQ coverage register and offline verification tools

Enterprise evaluation paths

EvaluatorStart hereWhat can be verified publicly
Enterprise architectReference architecture and scenario flowsSystem boundaries, governed request flow, deployment profiles, and responsibility split
Security or risk leadSecurity policy, PQ coverage register, and diligence indexDisclosure path, released PQ claims, evidence limitations, and public control references
Platform engineerAPI contracts, SDKs, MCP, and examplesIntegration contracts, install paths, source, examples, and client configuration
Procurement or technical diligenceMANIFEST.json, SHA256SUMS, SPDX SBOM, and NOTICEExport provenance, file integrity, package inventory, licensing, and the public/proprietary boundary

Architecture and scenarios

Start with the public reference architecture, then follow the control boundary through three concrete flows:

The matching visual architecture centre is published at bee.heossi.com/docs/architecture.

Bee Code's agent path is durable, subscription-bounded, and independently metered. Workspace, mobile, desktop, SDK, and MCP requests retain their own documented execution contracts; common entitlement enforcement does not imply that every surface has local IDE tools.

Integrity and provenance

The public distribution is locally rendered from an allowlisted monorepo surface. Verify it with:

bash
sha256sum --check SHA256SUMSpython3 scripts/verify_bee_package_index.py PACKAGE-INDEX.json

SHA256SUMS covers every exported payload file except itself and the commit-specific MANIFEST.json. The manifest separately binds the export to its source commit and contains a deterministic digest of the complete payload. The SPDX document is package-level (filesAnalyzed: false); it inventories the published SDK and MCP packages without claiming a binary or deployment SBOM.

Public and proprietary boundary

The files in this repository are Apache-2.0 licensed. Bee's model engine, orchestration plane, hosted gateway, Bee Code CLI implementation, editor-extension implementation, and commercial applications remain proprietary and are not represented as open source here. Public API and package behavior is defined by the contracts and SDK source in this repository.

Support and security

Contributing

Read CONTRIBUTING.md, SUPPORT.md, and the Code of Conduct. Generated paths must be changed in their canonical monorepo source; community examples and documentation can be proposed here and are reconciled during the next local export.

License

Apache License 2.0 · Copyright 2026 HEOSSI (Pte.) Ltd.

Bee™ and the Bee knot logo are trademarks of HEOSSI (Pte.) Ltd., Singapore.

來源:README.md,提交 42d3ffe

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

21
  1. v1.0.98最新Nov 3, 2026
  2. v1.0.97Nov 3, 2026
  3. v1.0.91Oct 31, 2026
  4. v1.0.79Oct 30, 2026
  5. v1.0.78Oct 30, 2026
  6. v1.0.77Oct 29, 2026
  7. v1.0.66Oct 26, 2026
  8. v1.0.65Oct 2, 2026
  9. v1.0.63Oct 1, 2026
  10. v1.0.57Sep 30, 2026
  11. v1.0.53Sep 30, 2026
  12. v1.0.48Sep 30, 2026
  13. v1.0.41Sep 28, 2026
  14. v1.0.40Sep 27, 2026
  15. v1.0.32Sep 26, 2026
  16. v1.0.29Sep 25, 2026
  17. v1.0.28Sep 25, 2026
  18. v1.0.27Sep 25, 2026
  19. v1.0.14Sep 24, 2026
  20. v1.0.13Sep 23, 2026
  21. v0.6.10Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分