Ext Ops Panel
Open dashboard
Comparison

AI Model Research vs DEEPBOM

AI Model Research is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). DEEPBOM is an MCP server published by JunHwan-Kwon. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-20. 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
MarketplaceAI Model ResearchDEEPBOM
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.5.0
Downloads/month (npm): 2 449
Downloads/week (npm): 277
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.4.0
Downloads/month (npm): 2 449
Downloads/week (npm): 277
Forks (GitHub): 0
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

AI Model Research vs DEEPBOM
FactAI Model ResearchDEEPBOM
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (model-scout-mcp)Remote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12Not a bundle
Licence (differs)MITApache-2.0
Repository (differs)github.com/danielrosehill/claude-ai-model-research-plugingithub.com/junhwan-kwon/deepbom
Changes in the last 7 days (differs)21
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

AI Model Research

In its own words, on Community GitHub marketplaces:

Research, discover, compare, and evaluate AI models on OpenRouter — backed by the bundled Model-Scout MCP server for live catalog data with caching. Subsumes the standalone open-router-model-research plugin and the Model-Scout-MCP server. 11 skills cover lookup, capability filtering (tools, vision, audio), recommendation, head-to-head comparison, deep evaluation, workload cost projection, and finding cheaper alternatives.

DEEPBOM

In its own words, on Official MCP Registry:

Browser-local and CLI static evidence for deployed AI model artifacts.

How to run each

AI Model Research As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install ai-model-research@danielrosehill

DEEPBOM As a remote MCP server

Claude Code
claude mcp add --transport http deepbom https://deepbom.org/mcp

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

Only DEEPBOM 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

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

What it can do: AI Model Research · What it can do: DEEPBOM · 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. 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