Verify API vs Verified Memory
Verify API is an MCP server published by mgdsn. Marketplaces we read that list it: 1 (Official MCP Registry). Verified Memory is an MCP server published by python1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
| Marketplace |  Verified Memory | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.0 No figure published Not marked · First seen |
Listed Version: 0.3.0 Downloads/month (npm): 139 Downloads/week (npm): 139 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
| Fact | Verify API | Verified Memory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (verify-api-mcp) | On your machine (@python1/verified-memory-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mgdsn/verify-api-mcp | github.com/python1/data-lore-hive |
| Changes in the last 7 days (differs) | 0 | 7 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
Verify API
Evidence-backed verification for citations, packages, repos, cases, filings, drugs, x402 sellers.
Verified Memory
Offline read-only search over a checksum-verified, optionally signed memory pack, with exact quotes
How to run each
Verify API As a local MCP server: PyPI package
claude mcp add --env "VERIFY_API_KEY=<YOUR_VERIFY_API_KEY>" --transport stdio verify-api-mcp -- uvx verify-api-mcpRequires: VERIFY_API_KEY (secret)
Verified Memory As a local MCP server: npm package
claude mcp add --transport stdio verified-memory -- npx -y @python1/verified-memory-mcp --pack "<YOUR_PACK>" --require-signature false --strict falseRequires: --pack
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
The marketplaces of Verified Memory publish no settings it asks for, so we do not compare settings.
What it can do: Verify API · What it can do: Verified Memory · 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.