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 分