Remote MCP · Endpoint

com.borisinc/memory MCP server

No. com.borisinc/memory answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mem.borisinc.com/mcp

The last check completed an MCP handshake.

Registry name
com.borisinc/memory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
768 ms
Tools exposed
8 tools
Uptime, last 30 days
84.2% from 19 checks
Described by its publisher as
Persistent agent memory paid per call via x402 USDC. Your wallet is your private memory namespace.
Listing
From the official MCP registry (active).
Recent checks of com.borisinc/memory
CheckedResultHandshake
1 hour agoHandshake completed768 ms
11 hours agoHandshake completed777 ms
1 day agoHandshake completed724 ms
2 days agoHandshake completed779 ms
4 days agoHandshake completed779 ms
4 days agoHandshake completed731 ms
5 days agoHandshake completed712 ms
6 days agoHandshake completed921 ms
8 days agoHandshake completed1.56 s
11 days agoHandshake completed1.03 s
13 days agoFailed - the request timed out—
16 days agoHandshake completed712 ms
18 days agoHandshake completed723 ms
20 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—
24 days agoHandshake completed1.29 s
26 days agoHandshake completed2.07 s
27 days agoHandshake completed1.11 s
29 days agoHandshake completed915 ms

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

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