memory-pulse

MCP server · npm · graded 2026-10-24Source linked

Give any agent self-improving memory you can trust in production. Every correction is kept, shown to your agent when it matters and enforced on Claude Code and Codex. Built-in memory security: notes cannot instruct the agent, and any edit to the record sh

No outside reports on file

memory-pulse reads local files; restrict its folder reach, network access, and credentials before installing.

Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for Memory Pulse helpful?

What it can access

Local filesReads & writes local foldersREVIEW
Command executionNo shell command runner notedLOW
Network reachConnects to outside service APINOTED
CredentialsNo API token requiredLOW
Package sourcenpm (memory-pulse)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

npx -y memory-pulse

All setup options ↓

Check this skill Watch it in my stack Compare Add to allowlist README badge View project

About Memory Pulse

Memory Pulse is an MCP server focused on Developer tools and Files & documents: Give any agent self-improving memory you can trust in production. Every correction is kept, shown to your agent when it matters and enforced on Claude Code and Codex. Built-in memory security: notes cannot instruct the agent, and any edit to the record sh.

It is published on npm as memory-pulse and hosted on GitHub at t-crew/memory-pulse (1,264 weekly npm downloads, last repository push on 2026-10-23). Based on its public metadata, its operational scope includes: reads local files.

Setup

Check these steps against the project’s own instructions before running anything.

Run memory-pulse with --ignore-scripts in claude_desktop_config.json or .cursor/mcp.json:

json

{
  "mcpServers": {
    "memory-pulse": {
      "command": "npx",
      "args": ["-y", "--ignore-scripts", "memory-pulse"]
    }
  }
}

Why this grade

CC — Moderate risk signals

Signal-based grade (2/7 points): public source code. This reflects adoption and transparency, not a code review.

Popularity and upkeep

28/100

Weekly npm downloads: 1.4k
Listing last refreshed: 2026-10-29

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Security reports

No reports found for this package in our research (last checked 2026-10-29).

Check a specific version →

Risks to watch for

Local file read access: Reads local documents or database files. Point it only at the specific files needed for the task so sensitive workspace files remain out of reach.
Dependency & version pinning: Distributed via npm (memory-pulse). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.

How to lower the risk

Least-privilege permissions

Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

Check its activity history or logs weekly at first, and look at what it changed or sent.
Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

It asks for more access than its job requires, or prompts you to paste passwords.
It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

How do I install Memory Pulse?

Run npx -y memory-pulse in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page. Full setup docs and environment variables are in github.com/t-crew/memory-pulse.

Are there security reports about Memory Pulse?

No reports found for this package in our research (last checked 2026-10-29). Memory Pulse currently holds Grade C (Moderate risk signals) based on public adoption and transparency signals. Key risk areas to watch include local file read access:, dependency & version pinning:.

Is Memory Pulse actively maintained?

Memory Pulse has 1.4k weekly npm downloads, with its latest repository commit pushed on 2026-10-23. Our directory data was last refreshed on 2026-10-29. Check recent commit activity, release tags, and open issues at github.com/t-crew/memory-pulse before pinning it in production.

What are alternatives to Memory Pulse?

You can compare Memory Pulse side by side with other Memory MCP servers in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.

Maintain or use Memory Pulse? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade C for Memory Pulse

GitHub README Markdown:

markdown

[![AgentArmorHQ Risk Grade for Memory Pulse](https://agentarmorhq.com/api/badge/t-crew-memory-pulse)](https://agentarmorhq.com/skills/t-crew-memory-pulse)

HTML embed:

html

<a href="https://agentarmorhq.com/skills/t-crew-memory-pulse"><img src="https://agentarmorhq.com/api/badge/t-crew-memory-pulse" alt="AgentArmorHQ Risk Grade for Memory Pulse" height="20" /></a>

Terminal check:

terminal

curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "t-crew-memory-pulse"

Share with your security lead

Need sign-off to use memory-pulse? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: memory-pulse
- **Listing URL:** https://agentarmorhq.com/skills/t-crew-memory-pulse
- **Type:** App connector
- **Risk Grade:** Grade C (Moderate risk signals)
- **Outside Security Advisories on File:** 0

#### Permission & Blast-Radius Signals
- **Local files:** Reads & writes local folders
- **Command execution:** No shell command runner noted
- **Network reach:** Connects to outside service API
- **Credentials:** No API token required
- **Package source:** npm (memory-pulse)

#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts memory-pulse`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type: App connector
Publisher: t-crew
Source code: github.com/t-crew/memory-pulse
Install command: npm install memory-pulse
Est. context load: ~750 tokens / turn (~4 tool schemas, 0.38% of 200k context)
Popularity: 1.4k weekly npm downloads
Last updated: 2026-10-29
Last graded: 2026-10-24

Community

Discussions for Memory Pulse

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for Memory Pulse helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude