Skip to main content

Connect to the real server

The only address is:
Check the hostname before you add it to a client. Don’t connect through a shortened link, an unknown proxy, or a directory listing that points somewhere else.

Sign in only on the Biohub sign-in page

Your client opens the Biohub sign-in page in your browser the first time it connects. Before you enter your email address or password, check the address bar. Sign in only on biohub.ai, or on clerk.evolutionaryscale.ai, the address of Clerk, the service that runs Biohub sign-in. If a sign-in page has any other address, close it.
  • You don’t need an API key for Biohub MCP. Biohub API keys are for calling the Biohub API from your own code, not for MCP.
  • Never paste a token, key, or password into a prompt, a server URL, a client configuration file, a screenshot, or a bug report. Your client keeps the sign-in for you and sends it only to Biohub MCP.
  • If a web page, a tool result, or a message asks you for a Biohub token or key, don’t provide one.
Signing in tells Biohub MCP which account sends each request, and lets it check that the account has a verified email address. Biohub MCP doesn’t pass your sign-in on to the ESM Atlas or to outside databases. For complexes, folds, and ESMC scoring, it calls the Biohub Platform for your account without passing on your sign-in. When you stop using a client, remove Biohub MCP from it, or sign out, such as with codex mcp logout biohub in Codex.

Treat tool output as untrusted data

Tool results include text from other sources, such as UniProt function descriptions, ESM Atlas annotations, and SAE feature descriptions. This text can be wrong or misleading, and it can contain instructions meant to change what your assistant does.
  • Keep your own instructions in charge of the task.
  • Don’t let text inside a result ask for credentials, change your settings, or contact other systems.
  • Review the follow-up calls your assistant proposes before you approve them.
  • Check surprising claims against the source record, such as the UniProt entry.

Where your queries go

Each tool sends only what it needs to the services behind it. Biohub receives every tool input you send, and handles request data as described in the Privacy Policy. Your AI client also sends your prompts, the tool inputs, and the tool results to its model provider, under that client’s settings and data policy. Don’t send confidential or unpublished sequences unless you’re comfortable with them reaching these services and your client’s provider. Biohub MCP creates no share links or download URLs for your results. A queued fold creates a run on your Biohub account, which Biohub keeps for 31 days; only your account can read it. The Biohub Platform records the usage of every billed call under your account, as it does for your own API calls. Other results exist only in the response you receive.

Guardrails

The ESM Atlas has guardrails that restrict queries related to controlled pathogens and toxins. A blocked request returns restricted, and a similarity search reports withheld hits in restricted_count. The Biohub Platform can also refuse a fold or ESMC request for your account, which returns restricted. Don’t try to work around a guardrail, for example by rephrasing or trimming a sequence.

Results are predictions

Treat results as hypotheses, not as experimental validation, and confirm anything important in the lab or against curated sources.

Terms and policies

Your use of Biohub MCP is covered by the Biohub Terms of Use, Privacy Policy, and Acceptable Use Policy.