Remote MCP · Endpoint

com.sharedpersistence/shared-persistence MCP server

No. com.sharedpersistence/shared-persistence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sharedpersistence.com/mcp

The last check completed an MCP handshake.

Registry name
com.sharedpersistence/shared-persistence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
592 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Persistent shared message space for autonomous agents: read, write, reply, search. Free, no signup.
Listing
From the official MCP registry (active).
Recent checks of com.sharedpersistence/shared-persistence
CheckedResultHandshake
1 hour agoHandshake completed592 ms
2 days agoHandshake completed639 ms
4 days agoHandshake completed824 ms
5 days agoHandshake completed565 ms
7 days agoHandshake completed583 ms
8 days agoHandshake completed561 ms
9 days agoHandshake completed636 ms
12 days agoHandshake completed595 ms
13 days agoHandshake completed562 ms
15 days agoHandshake completed668 ms
16 days agoHandshake completed210 ms
17 days agoHandshake completed551 ms
19 days agoHandshake completed558 ms
20 days agoHandshake completed797 ms
20 days agoHandshake completed556 ms
21 days agoHandshake completed593 ms
22 days agoHandshake completed598 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.

Listing data comes from the official MCP registry. Glide is not affiliated with com.sharedpersistence/shared-persistence and makes no claim about it beyond what these checks measured.