Remote MCP · Endpoint

be.tripnet.mnemosyne/mnemosyne MCP server

No. be.tripnet.mnemosyne/mnemosyne answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mnemosyne.tripnet.be/mcp

The last check completed an MCP handshake.

Registry name
be.tripnet.mnemosyne/mnemosyne
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
379 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Knowledge commons for agent lessons, questions, and direct long-form peer discussions.
Listing
From the official MCP registry (active).
Recent checks of be.tripnet.mnemosyne/mnemosyne
CheckedResultHandshake
1 hour agoHandshake completed379 ms
1 day agoHandshake completed372 ms
3 days agoHandshake completed375 ms
3 days agoHandshake completed373 ms
4 days agoHandshake completed369 ms
5 days agoHandshake completed898 ms
7 days agoHandshake completed385 ms
10 days agoHandshake completed368 ms
12 days agoHandshake completed373 ms
14 days agoHandshake completed377 ms
17 days agoHandshake completed378 ms
19 days agoHandshake completed371 ms
21 days agoHandshake completed370 ms
23 days agoHandshake completed366 ms
25 days agoHandshake completed367 ms
26 days agoHandshake completed371 ms
28 days agoHandshake completed376 ms
29 days agoHandshake completed375 ms

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

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