Ext Ops Panel
Open dashboard
Comparison

io.github.jerrysrodz/goldhold vs io.github.t-crew/memory-pulse

io.github.jerrysrodz/goldhold is an MCP server published by jerrysrodz. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.t-crew/memory-pulse is an MCP server published by t-crew. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.jerrysrodz/goldholdio.github.t-crew/memory-pulse
Official MCP Registry Listed
Version: 1.5.1
Downloads/month (npm): 178
Downloads/week (npm): 42
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.16.1
Downloads/month (npm): 1 217
Downloads/week (npm): 931
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.jerrysrodz/goldhold vs io.github.t-crew/memory-pulse
Factio.github.jerrysrodz/goldholdio.github.t-crew/memory-pulse
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-23
Where it runs (differs)Remote server (mcp.goldhold.ai/mcp)On your machine (memory-pulse)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/jerrysrodz/goldhold-mcp-servergithub.com/t-crew/memory-pulse
Changes in the last 7 days (differs)011
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days ago, requires a keyno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.jerrysrodz/goldhold

In its own words, on Official MCP Registry:

Persistent memory for AI agents. Search, store, and recall across sessions.

io.github.t-crew/memory-pulse

In its own words, on Official MCP Registry:

Give any agent self-improving memory you can trust in production. Built-in memory security.

How to run each

io.github.jerrysrodz/goldhold As a remote MCP server

Claude Code
claude mcp add --transport http goldhold https://mcp.goldhold.ai/mcp

Requires: GOLDHOLD_API_KEY (secret)

io.github.t-crew/memory-pulse As a local MCP server: npm package

Claude Code
claude mcp add --env "MEMORY_PULSE_KEY=<YOUR_MEMORY_PULSE_KEY>" --transport stdio memory-pulse -- npx -y memory-pulse

Requires: MEMORY_PULSE_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.jerrysrodz/goldhold has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.jerrysrodz/goldhold asks for

  • GOLDHOLD_API_KEY (secret)

Only io.github.t-crew/memory-pulse asks for

  • MEMORY_PULSE_BOARD
  • MEMORY_PULSE_KEY (secret)
  • MEMORY_PULSE_LEDGER

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.jerrysrodz/goldhold · What it can do: io.github.t-crew/memory-pulse · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built