A knowledgebase MCP server for biomedical research, part of the BioContextAI project.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-biocontext-ai-knowledgebase-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# BioContextAI - Knowledgebase MCP [](https://biocontext.ai/registry/biocontext-ai/knowledgebase-mcp) [](https://pypi.org/project/biocontext_kb/) [](https://github.com/biocontext-ai/knowledgebase-mcp) [](https://github.com/astral-sh/uv) [](https://github.com/astral-sh/ruff) [](https://github.com/pre-commit/pre-commit) [](https://github.com/biocontext-ai/knowledgebase-mcp/actions/workflows/ci.yaml) [](https://codecov.io/github/biocontext-ai/knowledgebase-mcp) A Model Context Protocol (MCP) server for biomedical research that provides a standardized connection layer between artificial intelligence systems and biomedical resources. Documentation and usage guides are available at: https://biocontext.ai ## Overview **BioContextAI Knowledgebase MCP** is an MCP server implementation for common biomedical resources, enabling agentic large language models (LLMs) to retrieve verified information and perform domain-specific tasks. Unlike previous approaches that required custom integration for each resource, BioContextAI KB MCP provides a unified access layer through the Model Context Protocol that enables interoperability between AI systems and domain-s…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.