Memory Pulse runs on your own machine — the client starts it, so there is no endpoint to ping. 325 installs a week from npm. Last commit 14 Sep 2026.
Corrections that outlive the session. A guard blocks the edit that writes the old value back.
Today is the operative word: we check Memory Pulse every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add memory-pulse -- npx -y memory-pulse
{
"mcpServers": {
"memory-pulse": {
"args": [
"-y",
"memory-pulse"
],
"command": "npx"
}
}
}
[mcp_servers.memory-pulse]
command = "npx"
args = ["-y", "memory-pulse"]
{
"mcpServers": {
"memory-pulse": {
"args": [
"-y",
"memory-pulse"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"memory-pulse": {
"args": [
"-y",
"memory-pulse"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
MEMORY_PULSE_KEY (License key (optional; free tier without one)).
The author declared them in the registry entry; get the values from the project itself.
Epistemic guard for AI coding: tracks uncertain values and blocks writes until verified.
An MCP server that exposes getMe key-value operations as MCP tools
FHIR MCP server with SMART Backend Services, response compaction, FHIRPath, and guarded writes.
WordPress edit previews, scoped correction checks, and change records for trusted operators.
Retrieval over the folder the session opened: files, search, read, code_pack, write_note.
MCP server that spawns and drives Claude Code sessions via claude-wrap.
A persistent Linux computer for your AI: what it installs and writes survives the session.
macOS computer use with the guardrails on: passwords blacked out, writes need consent, all logged.
Answers built from our own checks of this server.