Ext Ops Panel
Open dashboard
Comparison

MemoryLayer vs Agentverse Memory

MemoryLayer is an MCP server published by memorylayer.in. Marketplaces we read that list it: 1 (Official MCP Registry). Agentverse Memory is an MCP server published by fetchai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceMemoryLayerAgentverse Memory
Official MCP Registry Listed
Version: 1.7.1
Downloads/month (npm): 387
Downloads/week (npm): 34
Not marked · First seen
Listed
Version: 1.0.0
No figure published
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

MemoryLayer vs Agentverse Memory
FactMemoryLayerAgentverse Memory
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@raajvamsy/memorylayer)Remote server (am-server-jbneh74b5q-uc.a.run.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/fetchai/agentverse-memory
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

MemoryLayer

In its own words, on Official MCP Registry:

Local-first persistent memory for AI agents, with reasoning and formal verification.

Agentverse Memory

In its own words, on Official MCP Registry:

Graph-native persistent memory for AI agents — 33 MCP tools, zero-LLM writes.

How to run each

MemoryLayer As a local MCP server: npm package

Claude Code
claude mcp add --env "MEMORY_API_KEY=<YOUR_MEMORY_API_KEY>" --transport stdio memorylayer -- npx -y @raajvamsy/memorylayer

Requires: MEMORY_API_KEY (secret)

Agentverse Memory

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

The marketplaces of Agentverse Memory publish no settings it asks for, so we do not compare settings.

What it can do: MemoryLayer · What it can do: Agentverse 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.

Where the data comes from: how the catalog is built