BioTuring MCP

com.bioturingPublished by bioturing.comOfficial publisherv0.2.7Updated Nov 1, 2026

GPU-accelerated compute engine for BioTuring's biological databases

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

Remote MCP endpoint giving an assistant access to BioTuring's biological databases through a GPU-accelerated compute engine.

What you can do
  • The listing names no individual tools, so capabilities are known only at a high level.
  • Query BioTuring's biological databases through a GPU-accelerated compute engine.
  • Work with biological data held by the provider rather than local files.
When to use it
Worth considering when an assistant needs to work with BioTuring's biological databases and the provider's accelerated compute, for example in bioinformatics or life-science analysis sessions.
Requirements
A remote MCP endpoint at mcp.bioturing.com over streamable HTTP; OAuth authentication is required, so a BioTuring account with access to the service is needed. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth sign-in with BioTuring, so the assistant acts under your account. The listing does not describe which tools exist, whether queries are read-only, or what data is sent to the provider; confirm these before relying on it.

Installation

In SourceWeft

  1. Open BioTuring MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.bioturing%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bioturing": {
      "type": "http",
      "url": "https://mcp.bioturing.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.7LatestOct 31, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.