exo vs io.github.saxenakapil/setup-doctor
exo is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
exo is a plugin bundle for AI coding tools published by Thomas Hoogteijling. No marketplace we read lists it any more. io.github.saxenakapil/setup-doctor is an MCP server published by saxenakapil. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.saxenakapil/setup-doctor | |
|---|---|---|
| Community marketplace blauwtje/exo | Removed on 2026-10-15 Version: 0.133.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.3 Downloads/month (npm): 1 379 Downloads/week (npm): 58 Forks (GitHub): 1 Stars (GitHub): 2 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
| Fact | exono longer listed · | io.github.saxenakapil/setup-doctor |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 2 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (setup-doctor) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 7 | Not published |
| Parts of the bundle (differs) | 32 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/blauwtje/exo | github.com/saxenakapil/setup-doctor |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of exo
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Complete toolkit for building and distributing Claude Code plugins, skills, hooks, subagents, slash commands, marketplaces, and MCP servers
-
Evidence-first Claude Code plugin for repeatable, spec-driven development workflows.
-
Reusable architectural rules, skills, agents, and workflows for Claude Code.
-
Personal Claude Code configuration with 14 productivity commands and 11 specialized AI agents for modern web development
-
10 slash commands and 3 agent definitions distilled from 6 months of daily Claude Code use. Not a framework -- just the patterns that survived: multi-agent build pipelines…
-
23 reusable skills, 2 agents, and smart hooks for any project. Covers the full development cycle: architecture mapping, implementation planning, code review, safe refactoring…
What each says it does
exo
Claude Code plugin with four stages and hooks that refuse risky commands.
io.github.saxenakapil/setup-doctor
Score and improve your AI coding agent setup. Local-only, open source.
How to run each
exo
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.saxenakapil/setup-doctor As a local MCP server: npm package
claude mcp add --transport stdio setup-doctor -- npx -y setup-doctor mcpCommands 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: exo · What it can do: io.github.saxenakapil/setup-doctor · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.