Remote MCP · Endpoint

Olothea — Collective Mind & Human–AI Research MCP server

Yes, as of 16 hours ago: the server returned an HTTP error.

DownLast checked 16 hours ago

Server URL

https://olothea-research.vercel.app/api/mcp

The last check failed: the server returned an HTTP error.

Registry name
app.vercel.olothea-research/olothea
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
19 tools
Uptime, last 30 days
72.7% from 11 checks
Described by its publisher as
Emerging human–AI knowledge network: shared research, collective intelligence and peer review.
Listing
From the official MCP registry (active).
Recent checks of Olothea — Collective Mind & Human–AI Research
CheckedResultHandshake
16 hours agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed75 ms
17 days agoHandshake completed76 ms
19 days agoHandshake completed94 ms
20 days agoHandshake completed147 ms
21 days agoHandshake completed83 ms
22 days agoHandshake completed81 ms
22 days agoHandshake completed56 ms
24 days agoHandshake completed82 ms

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

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 Olothea — Collective Mind & Human–AI Research and makes no claim about it beyond what these checks measured.