Ext Ops Panel
Open dashboard
Comparison

Handoff Tracker vs Total Agent Memory

Handoff Tracker is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). Total Agent Memory is an MCP server published by vbcherepanov. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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
MarketplaceHandoff TrackerTotal Agent Memory
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 14.9.0
Downloads/month (PyPI): 1 668
Downloads/week (PyPI): 217
Forks (GitHub): 18
Stars (GitHub): 73
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

Handoff Tracker vs Total Agent Memory
FactHandoff TrackerTotal Agent Memory
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub73
Forks (GitHub) (differs)No figure on GitHub18
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server (handoff-tracker-mcp.vercel.app/api/mcp)On your machine (total-agent-memory)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Hooks it runs (differs)Not published9
Parts of the bundle (differs)Not a bundle12
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/vbcherepanov/total-agent-memory
Changes in the last 7 days (differs)06
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 402 (5 days ago)no 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

Handoff Tracker

In its own words, on Official MCP Registry:

Short-term session memory manager for collaborative agent networks.

Total Agent Memory

In its own words, on Official MCP Registry:

Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall

How to run each

Handoff Tracker As a remote MCP server

Claude Code
claude mcp add --transport sse handoff-tracker https://handoff-tracker-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: payment-signature header

Total Agent Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio total-agent-memory -- uvx total-agent-memory

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

Only Handoff Tracker 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

The marketplaces of Handoff Tracker publish no settings it asks for, so we do not compare settings.

What it can do: Handoff Tracker · What it can do: Total Agent Memory · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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