Mem0 Cloud

Name: Mem0 Cloud
Author: com.saastemly

MCP serverMCP

A hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):...

by com.saastemlyhomepage ↗v1.0.1791043972

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mem0-cloud","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability24/24 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	86 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
10 h ago	mcp initialize	ok	200	30 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
17 h ago	mcp initialize	ok	200	131 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
23 h ago	mcp initialize	ok	200	15 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
30 h ago	mcp initialize	ok	200	38 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	154 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	15 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	20 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	32 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools
3 d ago	mcp initialize	ok	200	31 ms	server mem0-cloud 1.0.0 · protocol 2025-06-18 · 4 tools

Tools observed via MCP handshake

add_memory — Store memories from a conversation, like mem0's add: an AI model extracts durable facts about the user from the messages (or, with infer=false, stores each mess
search_memories — Search your stored memories by meaning, like mem0's search: embeds the query and returns the closest memories with a relevance score from 0 to 1. Only memories
get_memories — Read your stored memories, like mem0's get memory and get all memories. With memory_id: returns that one memory (404 if it is not yours). Without it: returns a
delete_memories — Delete your stored memories, like mem0's delete memory and delete all memories. With memory_id: deletes that one memory (404 if it is not yours). Without it: de

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.saastemly/mem0-cloud

first seen 6 d ago · fetched 14 h agoopen ↗

Field history (6 recent events)

6 d ago · declared · summary → "A hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):..."
6 d ago · declared · description → "A hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):..."
6 d ago · declared · publisherName → "com.saastemly"
6 d ago · declared · homepageUrl → "https://mem0-cloud.saastemly.com"
6 d ago · declared · version → "1.0.1791043972"
6 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from