Ext Ops Panel
Open dashboard
Comparison

dev.veritap/agent-memory vs Hive Agent Storage

dev.veritap/agent-memory is an MCP server published by veritap.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Hive Agent Storage is an MCP server published by srotzin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacedev.veritap/agent-memoryHive Agent Storage
Official MCP Registry Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.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

dev.veritap/agent-memory vs Hive Agent Storage
Factdev.veritap/agent-memoryHive Agent Storage
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (locker.veritap.dev/mcp/memory)Remote server (hive-mcp-agent-storage.onrender.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/veritap-dev/veritap-lockergithub.com/srotzin/hive-mcp-agent-storage
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 days agoAnswered with HTTP 404 (5 days ago)

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

dev.veritap/agent-memory

In its own words, on Official MCP Registry:

Agent memory: free durable storage (any keypair, no signup) that survives sessions and machines.

Hive Agent Storage

In its own words, on Official MCP Registry:

Encrypted A2A object storage for autonomous agent state and artifacts

How to run each

dev.veritap/agent-memory As a remote MCP server

Claude Code
claude mcp add --transport http agent-memory https://locker.veritap.dev/mcp/memory

Hive Agent Storage As a remote MCP server

Claude Code
claude mcp add --transport http hive-mcp-agent-storage https://hive-mcp-agent-storage.onrender.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of dev.veritap/agent-memory responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: dev.veritap/agent-memory · What it can do: Hive Agent Storage · 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