Corollary — scientific AI models, tools and databases
REMOTE · COROLLARY-LABS.COM
Find open biology and chemistry AI models, bioinformatics tools and databases, and run them online.
Available components
Last scanned (15 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 681 tokens (~113/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://corollary-labs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=corollary-labs.com | CN=YR2,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | RSA 2048 | SHA256-RSA | 65d1e98ff25293ca52ef51bd794e8ca97f2 |
| SANs: corollary-labs.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of corollary-labs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| corollary-labs.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://corollary-labs.com/mcp | Verified | 200 | |
| http (plaintext) | http://corollary-labs.com/mcp | HTTPS enforced | 308 | https://corollary-labs.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_scientific_ai_for_task Compare the models or tools for a task ~102
For a task such as 'protein structure prediction', 'protein design', 'antibody design', 'molecular docking', 'single-cell', 'ADMET', 'phage genomics' or 'CRISPR', return every model or tool Corollary lists for it — what each does, licence, whether it runs online — and guidance on how to choose between them.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | The task, in plain words. |
No output schema declared.
No examples provided.
get_scientific_ai_details Explain one model, tool, database, pipeline or dataset ~112
Full reference for one entry: what it is, how it works, key facts, uses, strengths, limitations, citation, licence, and how to run it on Corollary. Pass a name ('RFdiffusion'), an id ('esmfold2', 'nf-core/rnaseq', 'facebook/esm2_t33_650M_UR50D') or a corollary-labs.com URL.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | Name, id or Corollary page URL. |
No output schema declared.
No examples provided.
how_to_run_science_task How to do a scientific analysis on Corollary ~143
For a piece of scientific work someone wants done — 'annotate a phage genome', 'deconvolve bulk RNA-seq into cell types', 'check assembly completeness', 'dock a ligand', 'fit an IC50', 'process accelerometer data', 'call variants', 'find CRISPR arrays' — return how it is done on Corollary: the stages in order, the programs, models and databases used, what commonly goes wrong, and the page that starts it. Use this when the user wants a task done rather than a model named.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | The work the user wants done, in plain words. |
No output schema declared.
No examples provided.
list_science_tasks List the analyses Corollary runs ~28
Every scientific analysis Corollary has a page and a method for, with its URL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_scientific_ai_tasks List the task categories ~31
The task categories Corollary compares models and tools in, with a page URL for each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_scientific_ai Search scientific AI models, tools, databases, pipelines and datasets ~196
Search Corollary's catalogue of open scientific AI models (protein structure prediction, protein design, docking, antibodies, genomics, single-cell, chemistry/ADMET, simulation, pathology, weather), bioinformatics programs (BUSCO, samtools, BLAST…), scientific databases (UniProt, PDB, gnomAD…), nf-core pipelines and datasets. Each result says what it does, its licence and whether it can be run online on Corollary with no GPU or installation, with the page URL. Use it when a user asks which model or tool to use for a biology or chemistry task, or where to run one.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Restrict to one kind. Default: any. |
| limit | integer | – | Default 10. |
| query | string | yes | Name or task, e.g. 'ESMFold', 'protein-ligand binding affinity', 'phage annotation'. |
No output schema declared.
No examples provided.
How do I install the Corollary — scientific AI models, tools and databases MCP server?
Corollary — scientific AI models, tools and databases is a hosted endpoint at https://corollary-labs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · corollary-labs.com
claude mcp add --transport http com-corollary-labs-corollary 'https://corollary-labs.com/mcp'
What is the Corollary — scientific AI models, tools and databases MCP server?
Corollary — scientific AI models, tools and databases is an MCP server listed in the public MCP registry as com.corollary-labs/corollary. Find open biology and chemistry AI models, bioinformatics tools and databases, and run them online. This page covers its hosted endpoint (https://corollary-labs.com/mcp).
Is the Corollary — scientific AI models, tools and databases MCP server safe to use?
Corollary — scientific AI models, tools and databases scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Corollary — scientific AI models, tools and databases MCP server expose?
Corollary — scientific AI models, tools and databases exposes 6 tools: search_scientific_ai, get_scientific_ai_details, compare_scientific_ai_for_task, how_to_run_science_task, list_science_tasks, list_scientific_ai_tasks. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.
Does the Corollary — scientific AI models, tools and databases MCP server require authentication?
No. We connected to Corollary — scientific AI models, tools and databases without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Corollary — scientific AI models, tools and databases MCP server still maintained?
Corollary — scientific AI models, tools and databases is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Corollary — scientific AI models, tools and databases MCP server?
VerifyMCP ran 13 checks on Corollary — scientific AI models, tools and databases, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.