Authentication and data use
This page collects how each UniBio Intelligence service authenticates a client, where the work is computed, and the limits on how results may be used.
How each service authenticates
| Service | Address | Authentication |
|---|---|---|
| UbiBiologics web pages | biologics.unibiointelligence.com | None for the model library, the tools catalog and the antibody explorer. An account is required to run a method or open project data. |
| UbiBiologics API | API Explorer | OAuth or a bearer credential. Discovery is public; execution and project data are authenticated. |
| UbiMCP, the MCP connection to UbiBiologics | https://mcp.unibiointelligence.com/mcp | OAuth, plus a grant issued for the client. |
| BioMed MCP, hosted instance | https://biomedmcp.unibiointelligence.com/mcp | None required to connect. The client signs in only when prompted, which raises the research allowance. |
| QSPQuest | Runs on your own computer | None for the engine itself. |
UbiMCP is the MCP route to UbiBiologics, so an LLM client needs only that one endpoint for projects, datasets, models, runs, artifacts and curated data. The UbiBiologics API remains the separate route for code that calls the application directly.
UbiMCP needs more than a successful sign-in. It restricts a caller to a granted set of operations, bound to one client and one resource and carrying an expiry, and a client without a valid grant receives an error naming the requirement rather than a result.
When a client first connects, an authorization page in the browser lists the scopes it requests and states that approving grants that application access to your account through the server. If calls still return the grant error afterwards, write to support@unibiointelligence.com, naming the client and the data or models it needs to reach.
Credentials belong in the secret storage of your client where it provides one. Do not paste a credential into a prompt or a shared configuration file.
Where the work is computed
- On UniBio Intelligence servers. The UbiBiologics workspace, its API, UbiMCP and the hosted BioMed MCP instance. Data uploaded to the workspace, requests sent to these endpoints, and the results computed from them are processed there.
- In your browser. A scenario run from the UbiBiologics model library, computed by QSPQuest compiled to WebAssembly.
- On your own computer. QSPQuest, including its local MCP server. Its models, requests and results stay on your machine.
In every case, an MCP client may send what it reads to the model provider it is configured to use. That is a property of your client, not of these services, and it applies even when the computation itself is local.
Research use
Output from these services is for research use only. None of them is a medical device, and their results must not be used for clinical diagnosis, treatment decisions or patient-specific prediction or dosing. Interpret each result within the assumptions and limitations stated for the method or model that produced it.
Do not submit identifiable patient data to any UniBio Intelligence service.
Records retrieved from public sources are observations and curated assertions made by those sources, not independent clinical validation. Where sources disagree, the disagreement is returned as it stands rather than resolved into a consensus.
Terms and reporting
- Terms of Service and Privacy Policy
- Suspected vulnerabilities: security@unibiointelligence.com. Do not include sensitive customer or patient data in an initial report.
- Other support: support@unibiointelligence.com