Ext Ops Panel
Open dashboard
Comparison

remember vs Wrench.Pro Vehicle Check

remember is a plugin bundle for AI coding tools published by Digital-Process-Tools. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). Wrench.Pro Vehicle Check is an MCP server published by wrench.pro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplacerememberWrench.Pro Vehicle Check
Claude Code: claude-plugins-official Listed
Version: 0.43.1
Forks (GitHub): 62
Stars (GitHub): 201
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.16.0
Forks (GitHub): 62
Stars (GitHub): 201
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

remember vs Wrench.Pro Vehicle Check
FactrememberWrench.Pro Vehicle Check
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)201No figure on GitHub
Forks (GitHub) (differs)62No figure on GitHub
Last release (differs)2026-10-20Not published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.wrench.pro/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)4Not published
Parts of the bundle (differs)6Not a bundle
Licence (differs)Community LicenseNot stated
Repository (differs)github.com/digital-process-tools/claude-rememberNot stated
Changes in the last 7 days (differs)50
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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

remember

In its own words, on Claude Code: claude-plugins-official:

Continuous memory for Claude Code. Extracts, summarizes, and compresses conversations into tiered daily logs. Claude remembers what you did yesterday.

Wrench.Pro Vehicle Check

In its own words, on Official MCP Registry:

Recalls, known issues, and honest maintenance costs for any US-market vehicle since 1990.

How to run each

remember As a Claude Code plugin

Claude Code
/plugin install remember@claude-plugins-official

Wrench.Pro Vehicle Check As a remote MCP server

Claude Code
claude mcp add --transport http vehicle-check https://mcp.wrench.pro/mcp

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

Only Wrench.Pro Vehicle Check 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

Neither one's marketplaces publish the settings it asks for.

What it can do: remember · What it can do: Wrench.Pro Vehicle Check · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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