Ext Ops Panel
Open dashboard
Comparison

io.github.Mars-proj/verifiable-memory vs Factum

io.github.Mars-proj/verifiable-memory is an MCP server published by Mars-proj. Marketplaces we read that list it: 1 (Official MCP Registry). Factum is an MCP server published by factum-project. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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.Mars-proj/verifiable-memoryFactum
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (PyPI): 114
Downloads/week (PyPI): 19
Not marked · First seen
Listed
Version: 0.1.3
Forks (GitHub): 0
Stars (GitHub): 3
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.Mars-proj/verifiable-memory vs Factum
Factio.github.Mars-proj/verifiable-memoryFactum
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (verifiable-memory-mcp)On your machine (factum-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/factum-project/factum
Changes in the last 7 days00
First seen2026-10-112026-10-11

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.Mars-proj/verifiable-memory

In its own words, on Official MCP Registry:

Memory for AI agents that can't hallucinate — cited or abstains, provable forget, deterministic.

Factum

In its own words, on Official MCP Registry:

Auditable memory for AI agents: provenance, cascade retraction, conflict refusal

How to run each

io.github.Mars-proj/verifiable-memory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio verifiable-memory -- uvx verifiable-memory-mcp

Factum

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

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: io.github.Mars-proj/verifiable-memory · What it can do: Factum · 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