Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BioCosm

REMOTE · BIOCOSM-MCP.FLY.DEV

Biotech intelligence for AI agents: drugs, targets, diagnostics, PoS estimates, and writeups.

0 this week 80 Trust /100

Last scanned (13 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1284 tokens (~98/item across 13 items; 13 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 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
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 0
    • Stability: 0.97 → pass security
  • 16 Oct 26 0
    • Stability: pass → 0.97 functional
  • 28 Sept 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
Diagnostics

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://biocosm-mcp.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 5e6e25e6df778e81cd07b85fc9f12d4df7d
SANs: *.fly.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of biocosm-mcp.fly.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
fly.dev. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://biocosm-mcp.fly.dev/mcp Verified 200
http (plaintext) http://biocosm-mcp.fly.dev/mcp HTTPS enforced 301 https://biocosm-mcp.fly.dev/mcp
MCP tools · 13 exposed · ~1,052 tokens

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 →

Tool Tokens
find_by_phase ~102

List drugs/diagnostics at a specific clinical phase.

NameTypeReqDescription
limitinteger–Maximum results (default 100, max 500)
node_type––Optional filter — "drug", "pipeline", "diagnostic", "target"
phasestringyesOne of "approved", "on_market", "phase3", "phase2", "phase1", "in_development", "cleared", "ldt", "ruo"
NameTypeReqDescription
resultarrayyes–

No examples provided.

find_by_target ~66

Find all drugs that target a specific gene/protein.

NameTypeReqDescription
limitinteger–Maximum results (default 50, max 200)
target_genestringyesGene symbol or target name (e.g. "EGFR", "KRAS", "PD-1")
NameTypeReqDescription
resultarrayyes–

No examples provided.

find_related ~145

Find nodes connected to a given node. Three relationship types are derived on-the-fly: - "drug_target": for a drug, the targets it hits (and vice versa for a target node, the drugs that hit it) - "same_company": drugs sharing a company with this node - "same_target_class": drugs with the same mechanism_class

NameTypeReqDescription
limitinteger–Maximum results per link type (default 30)
link_type––Optional filter — one of "drug_target", "same_target_class", "same_company". If None, returns all three groups.
node_idstringyesSource node identifier
NameTypeReqDescription
result–yes–

No examples provided.

get_company_portfolio ~50

Get a company's full drug/diagnostic portfolio from BioCosm.

NameTypeReqDescription
company_namestringyesCompany name (e.g. "Merck", "Roche", "Illumina")
NameTypeReqDescription
result–yes–

No examples provided.

get_coverage ~65

Report BioCosm's actual data coverage so you never mistake missing data for a real-world zero. An empty or absent field on a node means "not in BioCosm's data," never a true zero. BioCosm is AI-generated and may contain errors.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_node ~145

Get full details for a single BioCosm node: identity and all name aliases, classification, gene targets and mechanism, therapeutic areas, companies, revenue history where available (sparse: ~100 drugs, mostly blockbusters, as annualized quarterly estimates; source links when present), probability-of- success predictions for pipeline drugs (with confidence intervals and contributing factors), structured clinical trial outcomes, external cross-references, and writeup availability. Empty fields mean "not in BioCosm's coverage," NOT zero or absent in reality.

NameTypeReqDescription
node_idstringyesThe node identifier (e.g. "pembrolizumab", "trastuzumab")
NameTypeReqDescription
result–yes–

No examples provided.

get_node_freshness ~56

Get freshness details for a single node: writeup age, enrichment hash match, staleness score, validation score.

NameTypeReqDescription
node_idstringyesThe node identifier (e.g. "pembrolizumab")
NameTypeReqDescription
result–yes–

No examples provided.

get_pos_score ~68

Get the Probability of Success estimate for a node, including the base rate, adjustment factors with reasoning, confidence interval, and model version. Returns None for nodes without a PoS score (typically only late-stage pipeline drugs are scored).

NameTypeReqDescription
node_idstringyesNode identifier
NameTypeReqDescription
result–yes–

No examples provided.

get_staleness_report ~48

Get writeup staleness report: overall stats, top stale nodes, data source freshness.

NameTypeReqDescription
limitinteger–Number of top stale nodes to return (default 20)

Structured output declared, but exposes no named fields.

No examples provided.

get_stats ~44

Get a high-level overview of the BioCosm database: total nodes, writeups, companies, breakdowns by type/status/domain, validation scores, and recent pipeline runs.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_writeup ~55

Get the full writeup for a BioCosm node, including all sections, citations, structured data, and validation score.

NameTypeReqDescription
node_idstringyesThe node identifier (e.g. "pembrolizumab")
NameTypeReqDescription
result–yes–

No examples provided.

list_by_therapeutic_area ~62

List all nodes in a given therapeutic area.

NameTypeReqDescription
areastringyesTherapeutic area to search (e.g. "breast cancer", "non-small cell lung cancer")
limitinteger–Maximum results (default 50)
NameTypeReqDescription
resultarrayyes–

No examples provided.

search_nodes ~146

Search BioCosm nodes by name, gene symbol, target, therapeutic area, or company. Results are ranked: exact name/brand matches first, then partial name matches, with a node-type prior (canonical drug/diagnostic nodes rank above gene-target nodes, which rank above ChEMBL salt-form duplicates). Nodes matched only via description/company/area rank last. Each result includes a `name` field for disambiguation.

NameTypeReqDescription
limitinteger–Maximum results to return (default 20, max 100)
querystringyesSearch term (e.g. "breast cancer", "pembrolizumab", "Merck")
NameTypeReqDescription
resultarrayyes–

No examples provided.

Install

How do I install the BioCosm MCP server?

BioCosm is a hosted endpoint at https://biocosm-mcp.fly.dev/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 · biocosm-mcp.fly.dev

# add to Claude Code
claude mcp add --transport http nhoverte-biocosm 'https://biocosm-mcp.fly.dev/mcp'
Common questions

What is the BioCosm MCP server?

BioCosm is an MCP server listed in the public MCP registry as io.github.nhoverte/biocosm. Biotech intelligence for AI agents: drugs, targets, diagnostics, PoS estimates, and writeups. This page covers its hosted endpoint (https://biocosm-mcp.fly.dev/mcp).

Is the BioCosm MCP server safe to use?

BioCosm scores 80 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 BioCosm MCP server expose?

BioCosm exposes 13 tools: search_nodes, get_node, get_writeup, list_by_therapeutic_area, get_company_portfolio, and 8 more. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.

Does the BioCosm MCP server require authentication?

No. We connected to BioCosm without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BioCosm MCP server still maintained?

BioCosm 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 BioCosm MCP server?

VerifyMCP ran 12 checks on BioCosm, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BioCosm: Authorization. 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.