Remote MCP · Endpoint

Biolab MCP Server MCP server

No. Biolab MCP Server answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://srikarjy025-biolab-mcp.hf.space/mcp

The last check completed an MCP handshake.

Registry name
io.github.srikarjy/biolab-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
27 ms
Tools exposed
30 tools
Uptime, last 30 days
35.3% from 17 checks
Described by its publisher as
Auditable MCP server for PubMed, Europe PMC, ClinicalTrials.gov, and bioRxiv/medRxiv queries
Website
https://huggingface.co/spaces/srikarjy025/biolab-mcp
Repository
https://github.com/srikarjy/biolab-mcp-server
Listing
From the official MCP registry (active).
Recent checks of Biolab MCP Server
CheckedResultHandshake
2 hours agoHandshake completed27 ms
2 days agoHandshake completed31 ms
4 days agoHandshake completed81 ms
5 days agoHandshake completed38 ms
7 days agoHandshake completed27 ms
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed30 ms
13 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
23 days agoFailed - the server returned an HTTP error—

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 6 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Biolab MCP Server and makes no claim about it beyond what these checks measured.