Remote MCP · Endpoint

Memmo MCP server

No. Memmo answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://api.memmo.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.memmo/memmo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
35 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 10 checks
Described by its publisher as
Team memory for AI coding agents and code reviews, reviewed by humans and served over MCP.
Listing
From the official MCP registry (active).
Recent checks of Memmo
CheckedResultHandshake
3 days agoHandshake completed35 ms
6 days agoHandshake completed26 ms
16 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
21 days agoCredentials required—
22 days agoCredentials required—
24 days agoCredentials required—

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

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