Ext Ops Panel
Open dashboard
Comparison

Solumbe vs io.github.soluai-spa/solucortex-mcp

Solumbe is an MCP server published by BASHBOP. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.soluai-spa/solucortex-mcp is an MCP server published by soluai-spa. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceSolumbeio.github.soluai-spa/solucortex-mcp
Official MCP Registry Listed
Version: 4.8.0
Downloads/month (npm): 2 023
Downloads/week (npm): 661
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 1.1.2
Downloads/month (PyPI): 389
Downloads/week (PyPI): 32
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 4.8.0
Downloads/month (npm): 2 023
Downloads/week (npm): 661
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed

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

Solumbe vs io.github.soluai-spa/solucortex-mcp
FactSolumbeio.github.soluai-spa/solucortex-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-23Not published
Where it runs (differs)On your machine (@bashbop/solumbe)Remote server (mcp.solucortex.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/bashbop/solumbegithub.com/soluai-spa/solucortex-mcp
Changes in the last 7 days (differs)90
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days 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

Solumbe

In its own words, on Official MCP Registry:

Deterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.

io.github.soluai-spa/solucortex-mcp

In its own words, on Official MCP Registry:

Living technical memory for AI agents: recall approved project context, record what was learned.

How to run each

Solumbe As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio solumbe -- npx -y @bashbop/solumbe mcp

io.github.soluai-spa/solucortex-mcp As a remote MCP server

Claude Code
claude mcp add --transport http solucortex-mcp https://mcp.solucortex.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: SOLUCORTEX_API_KEY (secret), Authorization header

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

Only io.github.soluai-spa/solucortex-mcp 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 Solumbe publish no settings it asks for, so we do not compare settings.

What it can do: Solumbe · What it can do: io.github.soluai-spa/solucortex-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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