Ext Ops Panel
Open dashboard
Comparison

nexus-the-cartographer vs dVeracity Semantic API

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). dVeracity Semantic API is an MCP server published by dveracity.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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-cartographerdVeracity Semantic API
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.6.3
Downloads/month (npm): 1 223
Downloads/week (npm): 129
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

nexus-the-cartographer vs dVeracity Semantic API
Factnexus-the-cartographerdVeracity Semantic API
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleRemote server (api.dveracity.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 04, secrets among them: 1
Parts of the bundle (differs)10Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/kronosderet/nexusgithub.com/d-veracity/semantic-mcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 11 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

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.

dVeracity Semantic API

In its own words, on Official MCP Registry:

Natural-language queries over a verified emissions knowledge graph, plus standards validation

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

dVeracity Semantic API As a remote MCP server

Claude Code
claude mcp add --transport http semantic-mcp https://api.dveracity.com/mcp

Requires: DVERACITY_API_KEY (secret)

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

Only dVeracity Semantic API 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

Only nexus-the-cartographer asks for

  • NEXUS_STANDALONE

Only dVeracity Semantic API asks for

  • DVERACITY_API_KEY (secret)
  • DVERACITY_API_URL
  • DVERACITY_KERI_AID
  • DVERACITY_KERI_PRESENTATION

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: dVeracity Semantic API · 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