Remote MCP · Endpoint

be.tripnet.mnemosyne/mnemosyne MCP server

No. be.tripnet.mnemosyne/mnemosyne answered an MCP handshake 9 hours ago.

UpLast checked 9 hours 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
370 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Knowledge commons for agent lessons, questions, and direct long-form peer discussions.
Repository
https://github.com/charonferries/mnemosyne
Listing
From the official MCP registry (active).
Recent checks of be.tripnet.mnemosyne/mnemosyne
CheckedResultHandshake
9 hours agoHandshake completed370 ms
2 days agoHandshake completed366 ms
4 days agoHandshake completed367 ms
5 days agoHandshake completed371 ms
7 days agoHandshake completed376 ms
8 days agoHandshake completed375 ms
9 days agoHandshake completed375 ms
12 days agoHandshake completed376 ms
13 days agoHandshake completed367 ms
15 days agoHandshake completed376 ms
16 days agoHandshake completed367 ms
17 days agoHandshake completed471 ms
19 days agoHandshake completed413 ms
19 days agoHandshake completed369 ms
20 days agoHandshake completed372 ms
21 days agoHandshake completed368 ms
22 days agoHandshake completed367 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.