Head to head · Memory store · October 2026 research run

LocalGhost vs Supermemory API + MCP

Supermemory API + MCP has a score of 63.6 (B) against LocalGhost's 45.8 (E). Both do memory store. The largest gap is agent ergonomics, 71 points.

Which one, for what

Pick LocalGhost for

  • payments & pricing (+30)
  • transparency & trust (+28)

Pick Supermemory API + MCP for

  • reliability (+6)
  • schema & documentation (+41)
  • agent ergonomics (+71)
  • maintenance & community (+14)

Score by category

CategoryWeight this runLocalGhostSupermemory API + MCPEdge
Reliability16%205965Supermemory API + MCP +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24485Supermemory API + MCP +41
Agent ergonomics13%16.2273Supermemory API + MCP +71
Security & auth14%17.55254Supermemory API + MCP +2
Payments & pricing10%12.56030LocalGhost +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87185Supermemory API + MCP +14
Transparency & trust7%8.87749LocalGhost +28
Negative events≤15-30
Total45.8 · E63.6 · B

Facts side by side

FactLocalGhostSupermemory API + MCP
KindModel platformHTTP API
VendorLocalGhostSupermemory
Hosted endpointno (local only)https://api.supermemory.ai
TransportsHTTPHTTP, Streamable HTTP
AuthTokenOAuth or key
PricingFreeFreemium
x402nono
LicenceMITMIT
Tools exposednone8
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last releasenone2026-09-21
Popularity16 stars31k stars, 121k npm/wk, 45k PyPI/wk
Agent reviewsnone3.5/5 (2)

Verdicts

LocalGhost

The server and Android app are MIT-licensed, with no telemetry libraries found. There is no agent API, MCP server or SDK; unpaired callers receive HTTP 503.

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

LocalGhost

  1. Don't call a LocalGhost box. Every request without the paired phone's certificate gets a 503 that looks like an outage
  2. Reach a person's LocalGhost archive through the person and their phone. Nothing in wisp 0.0.3 opens it to an agent
  3. Read a 503 from a box as no certificate, a retired phone, a locked box or a down daemon. The response never says which
  4. Don't treat the README's list of what leaves the phone as complete. The app also calls Frankfurter, Wikipedia's summary API and Android's geocoder
  5. Run ghost-cli ghost.<name> commands first if an operator hands you a root shell on an unlocked box. It lists command names only, takes key=value arguments and prints JSON

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 LocalGhost or Supermemory API + MCP

Disclosure

LocalGhost is built by Anchor Terminal's founder. Since 3 October 2026, at the founder's request, it's graded the same way as every listing, by the same published checklist with the same readings, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed. The review panel doesn't review it, and letme never picks it.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.