Ext Ops Panel
Open dashboard
Comparison

neon vs dev.veritap/agent-memory

neon is a plugin bundle for AI coding tools published by neondatabase. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). dev.veritap/agent-memory is an MCP server published by veritap.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplaceneondev.veritap/agent-memory
Claude Code: claude-plugins-official Listed
Version: 2.0.1
Forks (GitHub): 21
Stars (GitHub): 101
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.1.1
Forks (GitHub): 21
Stars (GitHub): 101
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.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

neon vs dev.veritap/agent-memory
Factneondev.veritap/agent-memory
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)101 (better)0 (worse)
Forks (GitHub) (differs)21 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.neon.tech/mcp)Remote server (locker.veritap.dev/mcp/memory)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/neondatabase/agent-skillsgithub.com/veritap-dev/veritap-locker
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetResponded 30 h 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

neon

In its own words, on Claude Code: claude-plugins-official:

Manage your Neon projects and databases with the neon-postgres agent skill and the Neon MCP Server.

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.

How to run each

neon As a Claude Code plugin

Claude Code
/plugin install neon@claude-plugins-official

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

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

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

Only dev.veritap/agent-memory has a remote endpoint we 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: neon · What it can do: dev.veritap/agent-memory · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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