Ext Ops Panel
Open dashboard
Comparison

com.codician/growmos vs io.github.emergent-wisdom/understanding-graph

com.codician/growmos is an MCP server published by codician.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.emergent-wisdom/understanding-graph is an MCP server published by emergent-wisdom. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplacecom.codician/growmosio.github.emergent-wisdom/understanding-graph
Official MCP Registry Listed
Version: 0.1.5
Downloads/month (PyPI): 111
Downloads/week (PyPI): 31
Forks (GitHub): 2
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 0.1.32
Downloads/month (npm): 397
Downloads/week (npm): 99
Forks (GitHub): 0
Stars (GitHub): 1
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

com.codician/growmos vs io.github.emergent-wisdom/understanding-graph
Factcom.codician/growmosio.github.emergent-wisdom/understanding-graph
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (growmos)On your machine (understanding-graph)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/codician-team/growmosgithub.com/emergent-wisdom/understanding-graph
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

com.codician/growmos

In its own words, on Official MCP Registry:

Living knowledge graph for your repo: query with citations, remember/link facts, fact-check claims.

io.github.emergent-wisdom/understanding-graph

In its own words, on Official MCP Registry:

Persistent understanding via workflow prompts, typed updates, graph-native code, and supersession.

How to run each

com.codician/growmos As a local MCP server: PyPI package

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

io.github.emergent-wisdom/understanding-graph As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio understanding-graph -- npx -y understanding-graph 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

Neither one's marketplaces publish the settings it asks for.

What it can do: com.codician/growmos · What it can do: io.github.emergent-wisdom/understanding-graph · Compare two other plugins

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