Skip to content

BioCosm MCP server

io.github.nhoverte/biocosmnhovertestreamable-httpv1.0.0Scanned

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

13 tools: 13 only read.

Tools: 0 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BioCosm MCP server can do

The BioCosm MCP server is published by the GitHub account nhoverte. It has 13 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (get_stats).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Only reads 13Show 13 read-only tools
  • find_by_phaseList drugs/diagnostics at a specific clinical phase.No findings

    Why it is in this group

    • The name "find_by_phase" says "find": a word for reading.
    Description, as the server wrote it
    List drugs/diagnostics at a specific clinical phase.
  • find_by_targetFind all drugs that target a specific gene/protein.No findings

    Why it is in this group

    • The name "find_by_target" says "find": a word for reading.
    Description, as the server wrote it
    Find all drugs that target a specific gene/protein.
  • get_company_portfolioGet a company's full drug/diagnostic portfolio from BioCosm.No findings

    Why it is in this group

    • The name "get_company_portfolio" says "get": a word for reading.
    Description, as the server wrote it
    Get a company's full drug/diagnostic portfolio from BioCosm.
  • get_coverageReport BioCosm's actual data coverage so you never mistake missing data for a real-world zero.No findings

    Why it is in this group

    • The name "get_coverage" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_nodeGet full details for a single BioCosm node: identity and all name aliases, classification, gene targets and mechanism, therapeutic areas, companies, revenue history where available…No findings

    Why it is in this group

    • The name "get_node" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_node_freshnessGet freshness details for a single node: writeup age, enrichment hash match, staleness score, validation score.No findings

    Why it is in this group

    • The name "get_node_freshness" says "get": a word for reading.
    Description, as the server wrote it
    Get freshness details for a single node: writeup age, enrichment hash match, staleness score, validation score.
  • get_pos_scoreGet the Probability of Success estimate for a node, including the base rate, adjustment factors with reasoning, confidence interval, and model version.No findings

    Why it is in this group

    • The name "get_pos_score" says "get": a word for reading.
    Description, as the server wrote it
    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).
  • get_staleness_reportGet writeup staleness report: overall stats, top stale nodes, data source freshness.No findings

    Why it is in this group

    • The name "get_staleness_report" says "get": a word for reading.
    Description, as the server wrote it
    Get writeup staleness report: overall stats, top stale nodes, data source freshness.
  • get_statsGet a high-level overview of the BioCosm database: total nodes, writeups, companies, breakdowns by type/status/domain, validation scores, and recent pipeline runs.Reads private dataNo findings

    Why it is in this group

    • The name "get_stats" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "database": it reads databases.
    Description, as the server wrote it
    Get a high-level overview of the BioCosm database: total nodes, writeups, companies, breakdowns by type/status/domain, validation scores, and recent pipeline runs.
  • get_writeupGet the full writeup for a BioCosm node, including all sections, citations, structured data, and validation score.No findings

    Why it is in this group

    • The name "get_writeup" says "get": a word for reading.
    Description, as the server wrote it
    Get the full writeup for a BioCosm node, including all sections, citations, structured data, and validation score.
  • list_by_therapeutic_areaList all nodes in a given therapeutic area.No findings

    Why it is in this group

    • The name "list_by_therapeutic_area" says "list": a word for reading.
    Description, as the server wrote it
    List all nodes in a given therapeutic area.
  • search_nodesSearch BioCosm nodes by name, gene symbol, target, therapeutic area, or company.No findings

    Why it is in this group

    • The name "search_nodes" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Posture changes

  1. Nov 6, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18
  2. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 1 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 1 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http biocosm https://biocosm-mcp.fly.dev/mcp
claude mcp add --transport http biocosm https://biocosm-mcp.fly.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__biocosm__search_nodes",
      "mcp__biocosm__get_node",
      "mcp__biocosm__get_writeup",
      "mcp__biocosm__list_by_therapeutic_area",
      "mcp__biocosm__get_company_portfolio",
      "mcp__biocosm__get_stats",
      "mcp__biocosm__get_staleness_report",
      "mcp__biocosm__get_node_freshness",
      "mcp__biocosm__find_by_target",
      "mcp__biocosm__find_by_phase",
      "mcp__biocosm__find_related",
      "mcp__biocosm__get_pos_score",
      "mcp__biocosm__get_coverage"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as biocosm. Review it before you use it.

Capability tags behind 1 rule
  • mcp__biocosm__get_stats private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.nhoverte/biocosm/verify?hash=eac9f5baf1ad4e851314255a2e6a425dc3538f41da5d1b7cd1b082e248e08c65" | jq -e '.changed == false'

Pinned hash eac9f5baf1ad, from Nov 21, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.nhoverte/biocosm/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.nhoverte/biocosm
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.nhoverte/biocosm.svg)](https://radar.anlyon.com/servers/io.github.nhoverte/biocosm)

Source: MCP Registry. Synced Oct 21, 2026, 18:42 UTC.

BioCosm MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BioCosm MCP server safe?

No scan can promise that. What its definitions show: 13 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the BioCosm MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BioCosm MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BioCosm MCP server have?

13 tools: 13 read. search_nodes, get_node, get_writeup, list_by_therapeutic_area, get_company_portfolio, get_stats, get_staleness_report, get_node_freshness and 5 more.

Does the BioCosm MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BioCosm MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BioCosm MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.