Ext Ops Panel
Open dashboard
Comparison

nexus-agents vs io.github.rog0x/string

nexus-agents is a plugin bundle for AI coding tools published by williamzujkowski. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.rog0x/string is an MCP server published by rog0x. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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-agentsio.github.rog0x/string
Claude Code: claude-plugins-community Listed
Version: 2.33.0
Forks (GitHub): 2
Stars (GitHub): 20
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (npm): 136
Downloads/week (npm): 27
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-agents vs io.github.rog0x/string
Factnexus-agentsio.github.rog0x/string
Marketplaces that list it11
Stars (GitHub) (differs)20 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@rog0x/mcp-string-tools)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)31Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/williamzujkowski/nexus-agentsgithub.com/rog0x/mcp-string-tools
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-agents

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

Intelligent orchestration platform for AI coding tools. Coordinates Claude, Codex, Gemini, and OpenCode through a single MCP server — routing each task to the best model using data-driven algorithms (LinUCB bandit, TOPSIS scoring), validating outputs through multi-model consensus voting, and continuously improving through outcome-driven learning. Features 29 MCP tools, 11 expert types created on demand, 8 memory backends with cross-session persistence, a full dev pipeline (research, plan, vote, implement, QA, security), and research discovery from 9 sources including arXiv and GitHub.

io.github.rog0x/string

In its own words, on Official MCP Registry:

String analyzer, diff, templates for AI agents

How to run each

nexus-agents

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

io.github.rog0x/string As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio string -- npx -y @rog0x/mcp-string-tools

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: nexus-agents · What it can do: io.github.rog0x/string · 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