io.github.t-crew/memory-pulse
NPM · MEMORY-PULSE
Give any agent self-improving memory you can trust in production. Built-in memory security.
Available components
Last scanned (21 hours ago)
Scores higher than 93% of npm servers
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to t-crew/memory-pulse). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 580 tokens (~145/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- Package version: 0.7.0 → 0.16.1 functional
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- Package version: 0.15.1 → 0.16.1 functional
- Package version: 0.15.1 → 0.16.0 functional
- 22 Oct 26 +4
- Known CVEs: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: pass → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.14.3 → 0.15.1 functional
- Package version: 0.14.3 → 0.15.0 functional
- Package version: 0.14.3 → 0.14.4 functional
- 21 Oct 26 −14
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.10.0 → 0.14.3 functional
- Package version: 0.10.0 → 0.14.2 functional
- Package version: 0.10.0 → 0.13.1 functional
- Package version: 0.10.0 → 0.12.0 functional
- Package version: 0.10.0 → 0.11.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/memory-pulse@0.16.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | t-crew/memory-pulse |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/t-crew/memory-pulse/.github/workflows/release.yml@refs/tags/v0.16.1 |
| Rekor log index | 3414170699 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5ce699e55dfa8b9292b93067f544895c674b4b1d2c1d74c789215828b9d250990372768e46c03e124e5089da380dd91b52d34a5b99c42324e4b82b34f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
execute ~99
Run a JavaScript program against memory in a sandbox; ONLY its return value enters context. Use for questions needing many lookups — filtering, counting, cross-referencing — where the intermediates would otherwise cost more than the answer. `ctx.memory.effects|causes|pulse|when` are available and async. Example: return (await ctx.memory.effects('x')).hits.length
| Name | Type | Req | Description |
|---|---|---|---|
| program | string | yes | Body of an async function; must return. |
No output schema declared.
No examples provided.
pulse ~125
Re-enter a project without reading its history into context. Returns a salience-ranked brief that ALWAYS carries every recorded correction first, so a superseded number cannot be quoted by accident. Call this before answering questions about prior work.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Tokens you can spare for the brief. The brief is sized to fit; corrections always come first and whole. |
| root | string | – | Entity to centre the causal front on. |
| tier | string | – | index (smallest) → full. Default brief; omit it with `budget` to get the richest tier that fits. |
No output schema declared.
No examples provided.
recall ~122
Query the causal graph: what an event caused (effects), what caused it (causes), a multi-hop chain (pulse), or when a link was strongest (when). Hits carry a confidence; `exact` lists the recorded links verbatim, so a weak read never hides a correction. Returns nothing rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| object | string | – | Second entity — required by 'when', which scores an edge. |
| op | string | yes | – |
| subject | string | yes | Entity to query. |
| topk | number | – | Max hits. Default 5. |
No output schema declared.
No examples provided.
remember ~234
Record a finding so the next session starts with it. Use kind='correction' when a claim is withdrawn or a number is superseded — corrections are surfaced first at every tier and never decay. Cheap, idempotent, and fully local (works offline).
| Name | Type | Req | Description |
|---|---|---|---|
| cause | string | yes | – |
| effect | string | yes | – |
| kind | string | – | Default event. |
| note | string | – | What was measured, and how. |
| pinned | boolean | – | Never decays out of the brief. |
| replacement | array | – | For corrections: the corrected value(s). An edit containing both a withdrawn term and a replacement (a comparison or disavowal) is allowed through the guard. |
| scope | string | – | agent = the agent's own cross-project ledger (agent mode). |
| supersedes | array | – | For corrections: ledger t values of earlier corrections whose withdrawn terms no longer bind. |
| tags | array | – | – |
| withdrawn | array | – | For corrections: the exact strings that were withdrawn (a number, a name, a claim). The guard hook blocks an edit that writes them back. |
No output schema declared.
No examples provided.
How do I install the io.github.t-crew/memory-pulse MCP server?
io.github.t-crew/memory-pulse runs locally as an npm package, launched with npx -y memory-pulse. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · memory-pulse
claude mcp add t-crew-memory-pulse -- npx -y memory-pulse
What is the io.github.t-crew/memory-pulse MCP server?
io.github.t-crew/memory-pulse is an MCP server listed in the public MCP registry as io.github.t-crew/memory-pulse. Give any agent self-improving memory you can trust in production. Built-in memory security. This page covers its npm package (memory-pulse).
Is the io.github.t-crew/memory-pulse MCP server safe to use?
io.github.t-crew/memory-pulse scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.t-crew/memory-pulse MCP server expose?
io.github.t-crew/memory-pulse exposes 4 tools: pulse, recall, remember, execute. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.
Is the io.github.t-crew/memory-pulse MCP server still maintained?
io.github.t-crew/memory-pulse is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.t-crew/memory-pulse MCP server under?
io.github.t-crew/memory-pulse declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.