Ext Ops Panel
Open dashboard
Comparison

code-architecture-review vs io.github.andypgray/sliderule

code-architecture-review is a plugin bundle for AI coding tools published by Farjmand. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.andypgray/sliderule is an MCP server published by andypgray. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacecode-architecture-reviewio.github.andypgray/sliderule
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
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

code-architecture-review vs io.github.andypgray/sliderule
Factcode-architecture-reviewio.github.andypgray/sliderule
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleOn your machine (SlideRule.Cli)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/farjmand/code-architecture-reviewgithub.com/andypgray/sliderule
Changes in the last 7 days (differs)02
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

code-architecture-review

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

Drop this plugin into any project and ask Claude to "review my architecture." It scans for clean architecture violations, SOLID breaches, code smells, and structural anti-patterns across Node.js, Python, React, Go, and monorepo setups — then hands you a prioritized report with actionable fixes, not just vague warnings.

io.github.andypgray/sliderule

In its own words, on Official MCP Registry:

A .NET architecture checker that enforces one C# spec and renders the same rules for coding agents.

How to run each

code-architecture-review As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install code-architecture-review@claude-community

io.github.andypgray/sliderule

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

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

The marketplaces of code-architecture-review publish no settings it asks for, so we do not compare settings.

What it can do: code-architecture-review · What it can do: io.github.andypgray/sliderule · 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