Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"bioos": {
"env": {
"PYTHONPATH": "path/to/bioos-mcp-server/src",
"MIRACLE_ACCESS_KEY": "xxxxxxxxxxxx",
"MIRACLE_SECRET_KEY": "xxxxxxxxxxxx"
},
"args": [
"--directory",
"path/to/bioos-mcp-server",
"run",
"path/to/bioos-mcp-server/src/bioos_mcp/bioos_mcp_server.py"
],
"command": "path/to/uv"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) based tool and prompt server for Bio-OS that provides workflow management and Docker image building capabilities.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'uv' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
uv allows ZIP payload obfuscation through parsing differentials
## Impact In versions 0.8.5 and earlier of uv, remote ZIP archives were handled in a streamwise fashion, and file entries were not reconciled against the archive's central directory. This enabled two parser differentials against other Python package installers: 1. An attacker could contrive a ZIP archive that would extract with legitimate contents on some package installers, and malicious contents on others due to multiple local file entries. The attacker could choose which installer to target
uv is vulnerable to arbitrary file write through entry point names
### Impact In versions of uv prior to 0.11.15, when installing a distribution containing an entry point specification (under `console_scripts` or `gui_scripts`), uv would place the generated entry point according to the given name even if doing so resulted in a path outside of the environment's scripts directory. A malicious wheel could use this to place an executable outside of the intended environment, including in a directory already present on the user's `PATH`. This could shadow or overwr
uv vulnerable to arbitrary file deletion through RECORD entries
## Impact Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall. uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall. uv does not use the RECORD fi
PYSEC-2026-2295
A flaw was found in uv. This vulnerability allows an attacker to execute malicious code during package resolution or installation via specially crafted ZIP (Zipped Information Package) archives that exploit parsing differentials, requiring user interaction to install an attacker-controlled package.
uv has differential in tar extraction with PAX headers
### Impact In versions 0.9.4 and earlier of uv, tar archives containing PAX headers with file size overrides were not handled properly. As a result, an attacker could contrive a source distribution (as a tar archive) that would extract differently when installed via uv versus other Python package installers. The underlying parsing differential here originates with astral-tokio-tar, which disclosed this vulnerability as CVE-2025-62518. In practice, the impact of this vulnerability is **low**:
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in health / data
Manage Supabase projects — databases, auth, storage, and edge functions
Query and manage PostgreSQL databases directly from AI assistants
Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.
A Model Context Protocol (MCP) server that enables secure interaction with MySQL databases
MCP Security Weekly
Get CVE alerts and security updates for Bioos Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) based tool and prompt server for Bio-OS that provides workflow management and Docker image building capabilities.
We recommend using the CLINE extension for VSCode to interact with this MCP tool. There are two deployment options available: standalone installation on your local machine or using Code Server in a Miracle Cloud IES instance. Choose the option that best suits your needs.
Bio-OS MCP Server requires the following dependencies:
pip install uv
brew install cromwell
Clone the Bio-OS MCP Server repository:
git clone https://github.com/GBA-BI/bioos-mcp-server.git
Configure the Bio-OS MCP Server script path in CLINE's MCP settings. Replace the placeholders with absolute paths to your installation:
{
"mcpServers": {
"bioos": {
"command": "path/to/uv",
"args": [
"--directory",
"path/to/bioos-mcp-server",
"run",
"path/to/bioos-mcp-server/src/bioos_mcp/bioos_mcp_server.py"
],
"env": {
"PYTHONPATH": "path/to/bioos-mcp-server/src",
"MIRACLE_ACCESS_KEY": "xxxxxxxxxxxx",
"MIRACLE_SECRET_KEY": "xxxxxxxxxxxx"
}
}
}
}
Follow the configuration process shown below. The Bio-OS MCP Server is ready to use when the status turns green. If the connection is unstable, click "Retry Connection":

Since CLINE does not yet support MCP Prompts, copy the contents of bioos-mcp-prompt.md into CLINE's Custom Instructions for optimal experience:

After completing the configuration, you can begin using the Bio-OS MCP Server for development.
For Miracle Cloud users, we provide a pre-configured Docker image with all Bio-OS MCP Server dependencies. Follow these steps:
registry-vpc.miracle.ac.cn/infcprelease/iespro:250217

Click the CLINE icon in the left sidebar and configure your LLM model credentials:

Navigate to CLINE's MCP configuration page and verify that Bio-OS MCP Server is properly connected. Use "Retry Connection" if needed:

Once configured, you can begin development with Bio-OS MCP Server.
submit_workflow
import_workflow
validate_wdl
generate_inputs
build_docker_image