Remote MCP · Endpoint

com.borisinc/memory MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://mem.borisinc.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.borisinc/memory
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
77.8% from 18 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 agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoHandshake completed1.29 s
6 days agoHandshake completed2.07 s
7 days agoHandshake completed1.11 s
9 days agoHandshake completed915 ms
10 days agoHandshake completed1.56 s
11 days agoHandshake completed1.46 s
14 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed739 ms
17 days agoHandshake completed720 ms
18 days agoHandshake completed684 ms
19 days agoHandshake completed718 ms
20 days agoHandshake completed697 ms
21 days agoHandshake completed728 ms
22 days agoFailed - the server returned an HTTP error—
23 days agoHandshake completed735 ms
24 days agoHandshake completed685 ms

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

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.