Ext Ops Panel
Open dashboard
Comparison

nexus-the-cartographer vs io.github.bibinprathap/veritasgraph

nexus-the-cartographer is a plugin bundle for AI coding tools published by kronosderet. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.bibinprathap/veritasgraph is an MCP server published by bibinprathap. 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
Marketplacenexus-the-cartographerio.github.bibinprathap/veritasgraph
Claude Code: claude-plugins-community Listed
Version: 4.9.1
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (PyPI): 98
Downloads/week (PyPI): 32
Forks (GitHub): 39
Stars (GitHub): 324
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

nexus-the-cartographer vs io.github.bibinprathap/veritasgraph
Factnexus-the-cartographerio.github.bibinprathap/veritasgraph
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)324 (better)
Forks (GitHub) (differs)1 (worse)39 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (veritasgraph-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 03, secrets among them: 0
Parts of the bundle (differs)10Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/kronosderet/nexusgithub.com/bibinprathap/veritasgraph
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

nexus-the-cartographer

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

AI Cowork metabrain with Knowledge Graph, Thought Stack, Fuel Intelligence, and local AI Overseer. 20 native MCP tools for persistent session memory across Claude instances.

io.github.bibinprathap/veritasgraph

In its own words, on Official MCP Registry:

Zero-trust, air-gapped Enterprise GraphRAG MCP server with offline, citation-grounded answers.

How to run each

nexus-the-cartographer As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install nexus-the-cartographer@claude-community

io.github.bibinprathap/veritasgraph As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio veritasgraph -- uvx veritasgraph-mcp

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

Tools each declares

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

Settings each asks for

Only nexus-the-cartographer asks for

  • NEXUS_STANDALONE

Only io.github.bibinprathap/veritasgraph asks for

  • OLLAMA_HOST
  • STUDIO_DATA_DIR
  • VERITASGRAPH_MODEL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: nexus-the-cartographer · What it can do: io.github.bibinprathap/veritasgraph · Compare two other plugins

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