Ext Ops Panel
Open dashboard
Comparison

cogni-knowledge vs OntoRamp Knowledge Cartographer

cogni-knowledge is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑28.

cogni-knowledge is a plugin bundle for AI coding tools published by Stephan de Haas. No marketplace we read lists it any more. OntoRamp Knowledge Cartographer is an MCP server published by ontoramp.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecogni-knowledgeOntoRamp Knowledge Cartographer
Community marketplace cogni-work/insight-wave Removed on 2026-10-28
Version: 1.0.125
Forks (GitHub): 2
Stars (GitHub): 13
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

cogni-knowledge vs OntoRamp Knowledge Cartographer
Factcogni-knowledgeno longer listed · OntoRamp Knowledge Cartographer
Marketplaces that list it (differs)01
Stars (GitHub) (differs)130
Forks (GitHub) (differs)20
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (ontoramp-knowledge-cartographer.fly.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)37Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/cogni-work/insight-wavegithub.com/matthewdavisaiarchitect/ontoramp-knowledge-cartographer
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of cogni-knowledge

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • wiki-skills

    Skills implementing Karpathy's LLM Wiki pattern: wiki-init, wiki-ingest, wiki-query, wiki-lint, wiki-audit, wiki-update, wiki-merge

    by kfchou · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • knowledge-base

    Knowledge-base / wiki framework with skills for ingestion, query, and lint. Build a structured, citable corpus with cross-references and concept pages.

    by AIWG Contributors · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • mb

    Build and maintain a persistent AI-tended research wiki. Includes MCP server with 49 tools, slash commands, sub-agents, and an auto-context-injection hook.

    by Haobing Chu · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Mega Brain

    OKF-powered knowledge context for Claude Code

    by Gustavo Costa · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • llm-wiki

    A second brain for Claude Code + Obsidian inspired by Karpathy's LLM Wiki gist. Turn any LLM CLI into a disciplined wiki maintainer: incrementally ingest sources into a…

    by Alireza Rezvani · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • llmwiki

    Compile documents into a cited knowledge wiki. Retrieve evidence, query, and review via local MCP.

    by atomicstrata · MCP server

    Listed on: Official MCP Registry, npm registry (MCP servers) · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

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`.

OntoRamp Knowledge Cartographer

In its own words, on Official MCP Registry:

Knowledge coverage map and health score. Ingest docs into a governed knowledge graph via MCP.

How to run each

cogni-knowledge

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

OntoRamp Knowledge Cartographer As a remote MCP server

Claude Code
claude mcp add --transport http knowledge-cartographer https://ontoramp-knowledge-cartographer.fly.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only OntoRamp Knowledge Cartographer 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: cogni-knowledge · What it can do: OntoRamp Knowledge Cartographer · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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