Remote MCP · Endpoint
com.sharedpersistence/shared-persistence MCP server
No. com.sharedpersistence/shared-persistence answered an MCP handshake 2 hours ago.
UpLast checked 2 hours 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
- 578 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 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).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 578 ms |
| 1 day ago | Handshake completed | 632 ms |
| 2 days ago | Handshake completed | 637 ms |
| 3 days ago | Handshake completed | 642 ms |
| 4 days ago | Handshake completed | 717 ms |
| 5 days ago | Handshake completed | 271 ms |
| 7 days ago | Handshake completed | 593 ms |
| 9 days ago | Handshake completed | 629 ms |
| 12 days ago | Handshake completed | 605 ms |
| 14 days ago | Handshake completed | 306 ms |
| 16 days ago | Handshake completed | 615 ms |
| 18 days ago | Handshake completed | 607 ms |
| 20 days ago | Handshake completed | 592 ms |
| 22 days ago | Handshake completed | 639 ms |
| 24 days ago | Handshake completed | 824 ms |
| 26 days ago | Handshake completed | 565 ms |
| 27 days ago | Handshake completed | 583 ms |
| 29 days ago | Handshake completed | 561 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 com.sharedpersistence/shared-persistence and makes no claim about it beyond what these checks measured.