Ext Ops Panel
Open dashboard
Comparison

io.github.AINative-Studio/ainative-memory-mcp vs HippoDid MCP Server

io.github.AINative-Studio/ainative-memory-mcp is an MCP server published by AINative-Studio. Marketplaces we read that list it: 1 (Official MCP Registry). HippoDid MCP Server is an MCP server published by snowmanjy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
Marketplaceio.github.AINative-Studio/ainative-memory-mcpHippoDid MCP Server
Official MCP Registry Listed
Version: 1.0.1
Downloads/month (npm): 569
Downloads/week (npm): 216
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.1.0
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

io.github.AINative-Studio/ainative-memory-mcp vs HippoDid MCP Server
Factio.github.AINative-Studio/ainative-memory-mcpHippoDid MCP Server
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ainative-memory-mcp)On your machine (https://github.com/SameThoughts/hippodid-mcp-server/releases/download/v1.1.0/hippodid-mcp-server-1.1.0.jar)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/ainative-studio/ainative-memory-mcpgithub.com/samethoughts/hippodid-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

io.github.AINative-Studio/ainative-memory-mcp

In its own words, on Official MCP Registry:

Cloud-persistent, semantic-search memory MCP — drop-in for server-memory, backed by ZeroDB.

HippoDid MCP Server

In its own words, on Official MCP Registry:

Persistent, structured cloud memory for AI agents. BYOK — bring your own AI key.

How to run each

io.github.AINative-Studio/ainative-memory-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ainative-memory-mcp -- npx -y ainative-memory-mcp

HippoDid MCP Server

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 io.github.AINative-Studio/ainative-memory-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.AINative-Studio/ainative-memory-mcp · What it can do: HippoDid MCP Server · 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