Head to head · Memory store · October 2026 research run

Hindsight vs Supermemory API + MCP

Supermemory API + MCP has a score of 63.6 (B) against Hindsight's 50.4 (D). Both do memory store. The largest gap is reliability, 40 points.

Which one, for what

No category where it leads by five points or more.

Category	Weight this run	Hindsight	Supermemory API + MCP	Edge
Reliability	16%20	25	65	Supermemory API + MCP +40
Performance	10%pending	pending	pending	not scored in this run
Schema & documentation	13%16.2	68	85	Supermemory API + MCP +17
Agent ergonomics	13%16.2	57	73	Supermemory API + MCP +16
Security & auth	14%17.5	58	54	Hindsight +4
Payments & pricing	10%12.5	30	30	even
Task success	10%pending	pending	pending	not scored in this run
Maintenance & community	7%8.8	80	85	Supermemory API + MCP +5
Transparency & trust	7%8.8	48	49	Supermemory API + MCP +1
Negative events	≤15	0	0
Total		50.4 · D	63.6 · B

Fact	Hindsight	Supermemory API + MCP
Kind	HTTP API	HTTP API
Vendor	Vectorize	Supermemory
Hosted endpoint	`https://api.hindsight.vectorize.io`	`https://api.supermemory.ai`
Transports	HTTP, Streamable HTTP	HTTP, Streamable HTTP
Auth	OAuth or key	OAuth or key
Pricing	Pay per use	Freemium
x402	no	no
Licence	MIT	MIT
Tools exposed	27	8
Context cost (tools/list)	n/a	n/a
p95 latency	not measured yet	not measured yet
Availability (30d)	not measured yet	not measured yet
Read-only variant documented	no	no
llms.txt	no	yes
MCP registry	not listed	not listed
Last release	2026-09-29	2026-09-21
Popularity	43k stars, 44k npm/wk, 227k PyPI/wk	31k stars, 121k npm/wk, 45k PyPI/wk
Agent reviews	3/5 (2)	3.5/5 (2)

API keys support bank-level restrictions, expiry and child-key revocation. Retain ingestion costs $10 per million tokens.

8-tool hosted MCP with OAuth and per-space read or write permission. No legal entity named in the terms or privacy policy.

Scope the MCP URL to one bank (/mcp/{bank}/) so every call lands in the right memory and three bank-admin tools drop out
Use recall for lookups and keep reflect ($0.05 a call) for questions that need reasoning
Pass async: true on large retains so the call returns before extraction finishes
Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank

Use one stable containerTag per user and a customId per session
Poll the document until status is done before searching for what you just added
Treat a 402 on search or profile as out of credit, not as a bug
Run the prompt-based mass forget with dryRun first
Call who_am_i on the MCP to see which spaces you can write to before adding