Home / MCP registry index / io.github.srikarjy/biolab-mcp-server
Biolab MCP Server
io.github.srikarjy/biolab-mcp-server in the official MCP registry.
Endpoint https://srikarjy025-biolab-mcp.hf.space/mcp. Source: github.com/srikarjy/biolab-mcp-server.
The registry describes it as: Auditable MCP server for PubMed, Europe PMC, ClinicalTrials.gov, and bioRxiv/medRxiv queries
We read its 30 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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_evidence search fetch create_project list_projects create_evidence_collection list_evidence_collections add_evidence_to_collection get_evidence_collection create_evidence_watch list_evidence_watches run_evidence_watch list_evidence_events run_all_evidence_watches create_claim link_claim_evidence trace_claim get_project_report search_pubmed search_europepmc search_clinicaltrials search_biorxiv list_execution_tools run_tool get_execution list_executions get_artifact verify_executions replay_execution get_retrieval
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-srikarjy-biolab-mcp-server)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.