# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/hindsight-vs-supermemory
- Markdown: https://www.anchorterminal.com/compare/hindsight-vs-supermemory.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/compare/hindsight-vs-supermemory.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/hindsight-vs-supermemory.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

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.

- Hindsight: grade D, 50.4/100, rank #359 of 452. Markdown https://www.anchorterminal.com/tools/hindsight.md · JSON https://www.anchorterminal.com/api/v1/tools/hindsight.json
- Supermemory API + MCP: grade B, 63.6/100, rank #201 of 452. Markdown https://www.anchorterminal.com/tools/supermemory.md · JSON https://www.anchorterminal.com/api/v1/tools/supermemory.json

## Which one, for what

Pick Hindsight for nothing in particular (no category where it leads by five points or more).

Pick Supermemory API + MCP for reliability (+40), schema & documentation (+17), agent ergonomics (+16), maintenance & community (+5).

## Score by category

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

## Facts side by side

| 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) |

## Verdicts

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

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

## Before you call either

### Hindsight

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

### Supermemory API + MCP

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

## Other comparisons with Hindsight or Supermemory API + MCP

- [Cognee vs Hindsight](https://www.anchorterminal.com/compare/cognee-vs-hindsight.md)
- [Cognee vs Supermemory API + MCP](https://www.anchorterminal.com/compare/cognee-vs-supermemory.md)
- [Graphiti vs Hindsight](https://www.anchorterminal.com/compare/graphiti-vs-hindsight.md)
- [Graphiti vs Supermemory API + MCP](https://www.anchorterminal.com/compare/graphiti-vs-supermemory.md)
- [Hindsight vs Honcho](https://www.anchorterminal.com/compare/hindsight-vs-honcho.md)
- [Hindsight vs LocalGhost](https://www.anchorterminal.com/compare/hindsight-vs-localghost.md)
- [Hindsight vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/hindsight-vs-mem0.md)
- [Hindsight vs Zep](https://www.anchorterminal.com/compare/hindsight-vs-zep.md)
- [Honcho vs Supermemory API + MCP](https://www.anchorterminal.com/compare/honcho-vs-supermemory.md)
- [LocalGhost vs Supermemory API + MCP](https://www.anchorterminal.com/compare/localghost-vs-supermemory.md)
- [Mem0 Platform + MCP vs Supermemory API + MCP](https://www.anchorterminal.com/compare/mem0-vs-supermemory.md)
- [Supermemory API + MCP vs Zep](https://www.anchorterminal.com/compare/supermemory-vs-zep.md)