Remote MCP · Endpoint

BioCosm MCP server

No. BioCosm answered an MCP handshake 18 hours ago.

UpLast checked 18 hours ago

Server URL

https://biocosm-mcp.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.nhoverte/biocosm
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
30 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Biotech intelligence for AI agents: drugs, targets, diagnostics, PoS estimates, and writeups.
Listing
From the official MCP registry (active).
Recent checks of BioCosm
CheckedResultHandshake
18 hours agoHandshake completed30 ms
2 days agoHandshake completed32 ms
4 days agoHandshake completed38 ms
6 days agoHandshake completed53 ms
7 days agoHandshake completed39 ms
8 days agoHandshake completed33 ms
10 days agoHandshake completed27 ms
12 days agoHandshake completed53 ms
14 days agoHandshake completed26 ms
16 days agoHandshake completed41 ms
17 days agoHandshake completed48 ms
18 days agoHandshake completed35 ms
19 days agoHandshake completed45 ms
20 days agoHandshake completed27 ms
20 days agoHandshake completed27 ms
22 days agoHandshake completed29 ms
23 days agoHandshake completed242 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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.

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