Remote MCP · Endpoint

BioAI 日知 MCP server

No. BioAI 日知 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bioai-rizhi.pages.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.MInsYang/bioai-rizhi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
461 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read-only AI biopharma news, research records, companies, and source status from BioAI 日知.
Listing
From the official MCP registry (active).
Recent checks of BioAI 日知
CheckedResultHandshake
1 hour agoHandshake completed461 ms
1 day agoHandshake completed306 ms
2 days agoHandshake completed299 ms
2 days agoHandshake completed270 ms
4 days agoHandshake completed146 ms
7 days agoHandshake completed296 ms
9 days agoHandshake completed274 ms
12 days agoHandshake completed81 ms
14 days agoHandshake completed352 ms
16 days agoHandshake completed285 ms
18 days agoHandshake completed114 ms
20 days agoHandshake completed209 ms
22 days agoHandshake completed303 ms
24 days agoHandshake completed258 ms
25 days agoHandshake completed324 ms

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

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 BioAI 日知 and makes no claim about it beyond what these checks measured.