Ext Ops Panel
Open dashboard
Comparison

AgentWatchr vs agentmem

AgentWatchr is an MCP server published by agentwatchr.com. Marketplaces we read that list it: 1 (Official MCP Registry). agentmem is an MCP server published by Thezenmonster. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceAgentWatchragentmem
Official MCP Registry Listed
Version: 0.2.1
No figure published
Not marked · First seen
Listed
Version: 0.2.5
Downloads/month (PyPI): 137
Downloads/week (PyPI): 18
Forks (GitHub): 0
Stars (GitHub): 6
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

AgentWatchr vs agentmem
FactAgentWatchragentmem
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub6
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (agentwatchr.com/mcp)On your machine (quilmem)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/thezenmonster/agentmem
Changes in the last 7 days00
First seen (differs)2026-10-262026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (12 h 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

AgentWatchr

In its own words, on Official MCP Registry:

Read-only agent identity index with provenance, historical evidence and explained coverage.

agentmem

In its own words, on Official MCP Registry:

Governed memory for coding agents. Trust lifecycle, conflict detection, health scoring.

How to run each

AgentWatchr As a remote MCP server

Claude Code
claude mcp add --transport http evidence-index https://agentwatchr.com/mcp

agentmem As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio agentmem -- uvx quilmem --db ./memory.db --project myproject serve

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

Only AgentWatchr 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: AgentWatchr · What it can do: agentmem · 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