Ext Ops Panel
Open dashboard
Comparison

dev.veritap/locker vs io.github.Couchbase-Ecosystem/mcp-server-couchbase

dev.veritap/locker is an MCP server published by veritap.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Couchbase-Ecosystem/mcp-server-couchbase is an MCP server published by Couchbase-Ecosystem. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-19. 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/lockerio.github.Couchbase-Ecosystem/mcp-server-couchbase
Official MCP Registry Listed
Version: 0.3.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed, marked deprecated
Version: 0.8.0
Downloads/month (PyPI): 1 200
Downloads/week (PyPI): 247
Forks (GitHub): 34
Stars (GitHub): 34
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:85a104706d8b
Forks (GitHub): 34
Pulls (Docker Hub): 36 667
Stars (Docker Hub): 4
Stars (GitHub): 34
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/locker vs io.github.Couchbase-Ecosystem/mcp-server-couchbase
Factdev.veritap/lockerio.github.Couchbase-Ecosystem/mcp-server-couchbase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)34 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub36 667
Forks (GitHub) (differs)0 (worse)34 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (locker.veritap.dev/mcp)On your machine (couchbase-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)Not published20
Environment variables it asks for (differs)Not published33, secrets among them: 1
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/veritap-dev/veritap-lockergithub.com/couchbase-ecosystem/mcp-server-couchbase
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 28 h agono remote endpoint we check

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/locker

In its own words, on Official MCP Registry:

Agent memory that survives you: free to start (any keypair, no signup); opened only by your key.

io.github.Couchbase-Ecosystem/mcp-server-couchbase

In its own words, on Official MCP Registry:

Couchbase Model Context Protocol Server to interact with Couchbase clusters

How to run each

dev.veritap/locker As a remote MCP server

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

io.github.Couchbase-Ecosystem/mcp-server-couchbase As a local MCP server: PyPI package

Claude Code
claude mcp add --env "CB_PASSWORD=<YOUR_CB_PASSWORD>" --transport stdio mcp-server-couchbase -- uvx couchbase-mcp-server

Requires: CB_PASSWORD (secret)

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

Only dev.veritap/locker has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of dev.veritap/locker publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of dev.veritap/locker publish no settings it asks for, so we do not compare settings.

What it can do: dev.veritap/locker · What it can do: io.github.Couchbase-Ecosystem/mcp-server-couchbase · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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