Skip to content

BioContext7 Flagship

BioContext7 is the most mature product in the Hordago-Labs portfolio: a published @biocontext7/mcp package, an interactive /docs/api surface, a discoverable .well-known/mcp.json, and a maintained changelog, governance, and ADR kit. It keeps its own standalone site as the canonical source. This portal page is a flagship landing that summarizes and deep-links out — it never copies BioContext7's content, so the two never drift.

Canonical home

BioContext7 stays a public OSS project with its own site. Follow the deep links below to reach authoritative pages; this landing only orients you.

Destination What you get
Standalone site Canonical documentation home.
Interactive API Live /docs/api reference for the served routes.
MCP discovery .well-known/mcp.json manifest for client auto-configuration.
Changelog Release history for @biocontext7/mcp.
Governance & ADRs Governance kit and architecture decision records.

Registry

A searchable index of the bundles BioContext7 publishes. Each row pairs the served contract with the provenance manifest that attests to it. Use the portal search box to filter by bundle, contract, or manifest path.

Bundle Contract Provenance manifest
@biocontext7/mcp MCP tool catalog served at /docs/api .well-known/mcp.json
biocontext7-core Tool-selection evidence schema (query, tool, version, rationale) provenance/core.manifest.json
biocontext7-pipelines Pinned pipeline definitions with input/output format contracts provenance/pipelines.manifest.json
biocontext7-registry Bundle index contract (name, version, supported substrates) provenance/registry.manifest.json

Org Quality Bar

BioContext7's patterns are adopted as the Hordago-Labs quality bar (HD2):

  • Its mkdocs Material configuration is the portal theme base — the palette, navigation, and search features in this portal derive from it.
  • Its changelog, governance, and ADR kit is the org template for new bundles and DomainOS lanes.

Known drift (#7298)

BioContext7's OpenAPI v2 spec and its served routes are being reconciled. Treat the interactive API as authoritative for served behavior until #7298 closes the spec gap.