STEM — Persistent AI Memory MCP Server

by awase Your server? Claim it

answering

STEM — Persistent AI Memory is answering right now. Last checked 2 min ago.

Persistent memory and shared context across compatible AI assistants, with account-scoped OAuth.

Uptime history 8 hours of history

8 hours agonow

100.0%

Uptime 24h

26 of 26 checks

—

Tools

hidden behind auth

290 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check STEM — Persistent AI Memory every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add stem --transport http https://awase.dev/stem

Settings → Connectors → Add custom connector, then paste this address

https://awase.dev/stem

~/.codex/config.toml

[mcp_servers.stem]
url = "https://awase.dev/stem"

.cursor/mcp.json

{
  "mcpServers": {
    "stem": {
      "url": "https://awase.dev/stem"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "stem": {
      "type": "http",
      "url": "https://awase.dev/stem"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://awase.dev/stem	streamable-http	sign-in	246 ms	2 min ago

Alternatives to STEM — Persistent AI Memory

same job, measured the same way

MemoryRouter

by memoryrouter

Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.

10 tools answering

Openfuse MCP

by openfused

Encrypted mail, shared memory, and persistent context for AI agents.

15 installs/wk local only

Nexus Catalyst

by nexus-catalyst

Cross-tool persistent memory and context for AI assistants over MCP.

answering

MemoCat — Shared AI Memory

by montygovernance

One shared, persistent memory across AI agents and systems, with semantic recall and live updates.

173 installs/wk local only

Memphora

by memphora

Add persistent memory to AI assistants. Store and recall info across conversations.

110 installs/wk local only

Brains

by brainsforai

Personal wiki and memory layer for AI assistants. Persistent, structured memory across sessions.

answering

Memory

by velixarai

Persistent memory for AI assistants. Store, search, and recall across sessions.

31 installs/wk local only

Brain Memory

by brainmemory

Persistent memory for AI agents: one brain shared across Claude, Cursor, Codex and more.

answering

STEM — Persistent AI Memory — questions

Answers built from our own checks of this server.

Why is there no tool list for STEM — Persistent AI Memory?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is STEM — Persistent AI Memory working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 26 of 26 checks got a reply (100.0%), average response time 290 ms. The bar chart above shows every period we have measured.

How do I connect STEM — Persistent AI Memory?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to STEM — Persistent AI Memory?

No API key is involved. STEM — Persistent AI Memory answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is STEM — Persistent AI Memory?

It answers our handshake in 290 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.