Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bee: Quantum Intelligence

PYPI · BEE-SDK · 2 COMPONENTS

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

+15 this week 86 Trust /100

Last scanned (5 hours ago)

Scores higher than 89% of PyPI servers

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1512 tokens (~75/item across 20 items; 16 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.0.91 → 1.0.98 functional
    • Package version: 1.0.91 → 1.0.97 functional
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 1.0.79 → 1.0.91 functional
  • 30 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 1.0.77 → 1.0.79 functional
    • Package version: 1.0.77 → 1.0.78 functional
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: 1.0.71 → 1.0.77 functional
    • Package version: 1.0.71 → 1.0.74 functional
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 1.0.67 → 1.0.71 functional
    • Package version: 1.0.67 → 1.0.70 functional
    • Package version: 1.0.67 → 1.0.69 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/bee-sdk@1.0.98

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~1,423 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bee_chat ~124

Use for general or specialist questions that do not require a more specific Bee tool. Returns generated text from the selected domain and model tier. The gateway enforces the API key's plan, tenant policy, token allowance, and usage metering.

NameTypeReqDescription
domainstring–Optional domain specialist (defaults to general).
max_tokensinteger–Max response tokens
messagestringyesThe question or request
modelstring–Optional Bee model tier. Limited to your plan. Default: bee-cell.
temperaturenumber–Sampling temperature (optional)

No output schema declared.

No examples provided.

bee_code ~130

Use for code explanation, bug fixing, refactoring, or test generation. Returns text and proposed code; it does not read files, execute commands, or modify a repository. Choose the intended operation with action.

NameTypeReqDescription
actionstringyesWhat to do with the code
codestringyesThe code
errorstring–Error message / bug description (for action=fix)
focusstring–What to optimise for (for action=refactor)
frameworkstring–Test framework (for action=write_tests)
languagestring–Programming language

No output schema declared.

No examples provided.

bee_computer_use_validate_host ~102

Use to validate a real Bee computer-use host capability report and optional governed action request at the hosted gateway. This tool does not observe a screen, control input, automate a device, or create a local driver; execution must happen in a verified host runtime with explicit capability evidence.

NameTypeReqDescription
hostobjectyesBee computer-use host report using protocol bee.computer.v1.
requestobject–Optional Bee computer-use action request with approval evidence.

No output schema declared.

No examples provided.

bee_documents_add ~77

Use only when the user intends to persist supplied text in the authenticated tenant's hosted Bee knowledge base. Creates a searchable document and consumes the plan's document allowance; it does not read local files by itself.

NameTypeReqDescription
contentstringyesThe document text to ingest
sourcestring–A name / source label for the document

No output schema declared.

No examples provided.

bee_documents_search ~66

Use to retrieve relevant excerpts from the authenticated tenant's hosted Bee document library. Returns ranked chunks and source labels without changing the library; requires a RAG-entitled plan.

NameTypeReqDescription
kinteger–How many chunks to return
querystringyesWhat to search for

No output schema declared.

No examples provided.

bee_memory_add ~76

Use only when the user intends Bee to persist a fact for future conversations. Writes to the authenticated user's memory, honors opt-in and tenant policy, and automatically suppresses near-duplicates.

NameTypeReqDescription
contentstringyesThe fact to remember (≤ 4000 chars)
kindstring–What kind of memory this is

No output schema declared.

No examples provided.

bee_memory_search ~66

Use to recall facts, preferences, projects, or skills from the authenticated user's Bee memory. Returns ranked memories without changing them and honors the user's memory setting and tenant policy.

NameTypeReqDescription
querystringyesWhat to recall
top_kinteger–How many memories to return

No output schema declared.

No examples provided.

bee_quantum_reasoning_get ~57

Use to inspect one tenant-scoped Lab job. Returns status, candidates, scores, result, QPU or fallback evidence, usage, and receipt ID without changing the job.

NameTypeReqDescription
job_idstringyesJob UUID

No output schema declared.

No examples provided.

bee_quantum_reasoning_jobs ~73

Use to list the authenticated tenant's retained Quantum Reasoning Lab jobs and capabilities. Returns paginated metadata without creating or changing jobs.

NameTypeReqDescription
cursorstring–Opaque cursor from the previous page
limitinteger––
modelstring––
statusstring––

No output schema declared.

No examples provided.

bee_quantum_reasoning_remove ~51

Use only after explicit user intent to cancel an eligible queued job or permanently erase content from a terminal job. This is a destructive, tenant-scoped operation.

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

bee_quantum_reasoning_run ~98

Use only after the user chooses an eligible hosted quantum product. Creates a durable, tenant-encrypted, metered Quantum Reasoning Lab job that may incur simulator or QPU cost. Returns a job record; inspect it with bee_quantum_reasoning_get.

NameTypeReqDescription
modelstringyes–
productstringyes–
promptstringyesThe problem and decision criteria
provider_connection_idstring––

No output schema declared.

No examples provided.

bee_research ~116

Use to draft a NISQ-honest quantum-circuit design or critique an ML/CS paper. Returns research text or sample framework code; it does not submit QPU work. Use bee_quantum_reasoning_run for a durable hosted Lab job.

NameTypeReqDescription
focusstring–Critique focus (for paper_critique)
frameworkstring–Quantum framework (for quantum_design)
inputstringyesThe task to design, or the abstract to critique
taskstringyesResearch task

No output schema declared.

No examples provided.

bee_security ~138

Use for defensive code audits, threat models, authorized penetration-test support, or smart-contract review. Returns analysis and remediation guidance only; it does not scan a target or execute exploits and refuses unauthorized weaponization.

NameTypeReqDescription
contextstring–Authorised-engagement scope (for task=pentest_assist)
frameworkstring–Framework (for task=threat_model): STRIDE, PASTA, LINDDUN
inputstringyesCode, system description, contract source, or finding
languagestring–Language (for code_audit / smart_contract_review)
taskstringyesSecurity task

No output schema declared.

No examples provided.

bee_smith_assurance ~93

Commission Smith for an evidence-first critical-systems assurance review of a customer-owned or explicitly authorized target. A Bee-operated run is internal automated assurance, not government certification or an external-independent audit.

NameTypeReqDescription
authorization_scopestringyesCustomer ownership or written authorization and exact boundary
evidencestringyes–
profilestring––
targetstringyes–
taskstringyes–

No output schema declared.

No examples provided.

bee_usage ~83

Use to inspect the authenticated caller's Bee plan and metered consumption. Returns pooled tokens, per-tier allowances, reset times, and a 24-hour or 7-day breakdown. It never changes billing, credits, or entitlements.

NameTypeReqDescription
windowstring–Breakdown window: 'day' (24h) or 'week' (7d). Default 'day'.

No output schema declared.

No examples provided.

bee_verify_provenance ~73

Use to verify a Bee agentic coding session by session_id. Returns verification status, sealed-turn count, and ML-DSA-65 (NIST FIPS 204) signature details; it does not alter or replay the session.

NameTypeReqDescription
session_idstringyesThe agent session id to verify

No output schema declared.

No examples provided.

Install

How do I install the Bee: Quantum Intelligence MCP server?

Bee: Quantum Intelligence runs locally as a PyPI package, launched with uvx bee-sdk. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · bee-sdk

# add to Claude Code
claude mcp add heossihq-bee-public -- uvx bee-sdk
Common questions

What is the Bee: Quantum Intelligence MCP server?

Bee: Quantum Intelligence is an MCP server listed in the public MCP registry as io.github.heossihq/bee-public. Bee governed intelligence for chat, code, research, documents, and memory. This page covers its PyPI package (bee-sdk).

Is the Bee: Quantum Intelligence MCP server safe to use?

Bee: Quantum Intelligence scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Bee: Quantum Intelligence MCP server expose?

Bee: Quantum Intelligence exposes 16 tools: bee_chat, bee_code, bee_security, bee_smith_assurance, bee_research, and 11 more. Their descriptions and schemas cost roughly 1,423 tokens of context every time the server is loaded.

Is the Bee: Quantum Intelligence MCP server still maintained?

Bee: Quantum Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Bee: Quantum Intelligence MCP server under?

Bee: Quantum Intelligence declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.