Home / MCP registry index / io.github.nhoverte/biocosm
BioCosm
io.github.nhoverte/biocosm in the official MCP registry.
Endpoint https://biocosm-mcp.fly.dev/mcp.
The registry describes it as: Biotech intelligence for AI agents: drugs, targets, diagnostics, PoS estimates, and writeups.
We read its 13 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_nodes get_node get_writeup list_by_therapeutic_area get_company_portfolio get_stats get_staleness_report get_node_freshness find_by_target find_by_phase find_related get_pos_score get_coverage
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-nhoverte-biocosm)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.