Ext Ops Panel
Open dashboard
Comparison

Needle Remote vs cogni-knowledge

Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). cogni-knowledge is a plugin bundle for AI coding tools published by Stephan de Haas. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
MarketplaceNeedle Remotecogni-knowledge
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace cogni-work/insight-wave Not listed Listed
Version: 1.0.125
Forks (GitHub): 2
Stars (GitHub): 13
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

Needle Remote vs cogni-knowledge
FactNeedle Remotecogni-knowledge
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub13
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.needle.app/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle37
LicenceApache-2.0Apache-2.0
Repository (differs)Not statedgithub.com/cogni-work/insight-wave
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)Answered with HTTP 301 (13 h ago)no 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

Needle Remote

In its own words, on Docker MCP Catalog:

Production-ready RAG service to search and retrieve data from your documents.

cogni-knowledge

In its own words, on Community GitHub marketplaces:

Wiki-first research that compounds. Binds each run to a wiki knowledge base; future runs read what prior runs filed before hitting the web. v0.1.0 inverted pipeline (plan → curate → fetch → ingest → distill → compose → verify → finalize) with zero-network, citation-consistent claim verification — opt-in live-source resweep via `knowledge-refresh --resweep`. The shallow `knowledge-query` rung is read-only by default and can optionally file its answer back as an un-verified synthesis page via `--file-back`.

How to run each

Needle Remote As a remote MCP server

Claude Code
claude mcp add --transport http needle https://mcp.needle.app/mcp

Requires: NEEDLE_API_KEY (secret)

cogni-knowledge As a Claude Code plugin

Claude Code
/plugin marketplace add cogni-work/insight-wave
/plugin install cogni-knowledge@insight-wave

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

Only Needle Remote 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

The marketplaces of cogni-knowledge publish no settings it asks for, so we do not compare settings.

What it can do: Needle Remote · What it can do: cogni-knowledge · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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