Remote MCP · Endpoint

Cerebrum MCP server

No. Cerebrum answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://askcerebrum.org/mcp

The last check completed an MCP handshake.

Registry name
org.askcerebrum/cerebrum
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
331 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search the scientific literature and get a cited answer, plus the Trending in Science edition.
Listing
From the official MCP registry (active).
Recent checks of Cerebrum
CheckedResultHandshake
13 minutes agoHandshake completed331 ms
10 days agoHandshake completed362 ms
10 days agoHandshake completed539 ms
11 days agoHandshake completed471 ms
13 days agoHandshake completed346 ms
14 days agoHandshake completed377 ms
14 days agoHandshake completed343 ms
15 days agoHandshake completed467 ms
17 days agoHandshake completed309 ms
19 days agoHandshake completed3.48 s
21 days agoHandshake completed370 ms
24 days agoHandshake completed276 ms
26 days agoHandshake completed310 ms
28 days agoHandshake completed260 ms

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

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