Remote MCP · Endpoint

Configure Memory MCP server

No. Configure Memory answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.configure.dev/

The last check completed an MCP handshake.

Registry name
io.github.configure-dev/configure-memory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
251 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Bring your saved preferences, project decisions, and useful context into your next AI conversation.
Listing
From the official MCP registry (active).
Recent checks of Configure Memory
CheckedResultHandshake
1 hour agoHandshake completed251 ms
2 days agoHandshake completed205 ms
5 days agoHandshake completed227 ms
7 days agoHandshake completed172 ms
9 days agoHandshake completed228 ms
11 days agoHandshake completed140 ms
13 days agoHandshake completed209 ms
15 days agoHandshake completed210 ms
17 days agoHandshake completed137 ms
19 days agoHandshake completed180 ms
20 days agoHandshake completed156 ms
21 days agoHandshake completed235 ms
23 days agoHandshake completed174 ms

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

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