Ext Ops Panel
Open dashboard
Comparison

LLM Text vs Text Corpus Analysis

LLM Text is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Text Corpus Analysis is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
MarketplaceLLM TextText Corpus Analysis
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace danielrosehill/claude-code-plugins Not listed Listed
Version: 0.1.0
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

LLM Text vs Text Corpus Analysis
FactLLM TextText Corpus Analysis
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.llmtxt.dev/sse)Installs as a plugin bundle
Transport (differs)SSENot stated
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle14
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/danielrosehill/claude-text-corpus-analysis-plugin
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)Not responding since 2026-10-13no remote endpoint we check

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

LLM Text

In its own words, on Docker MCP Catalog:

Discovers and retrieves llms.txt from websites.

Text Corpus Analysis

In its own words, on Community GitHub marketplaces:

Skills for analyzing large text corpora — topic modeling (BERTopic with temporal evolution), NER, categorization into fixed taxonomies, bottom-up category derivation, multi-level taxonomy design, word frequency, synonym clustering for voice-note/STT corpora, parametric stats, and metadata↔content correlation. Three execution lanes (classical NLP, local LLM via Ollama, cloud LLM via OpenRouter) with explicit cost-awareness: mandatory pre-run estimates for >1k-doc LLM passes, two-pass cheap→premium pattern, embeddings+clustering preferred over pairwise LLM comparison.

How to run each

LLM Text As a remote MCP server

Claude Code
claude mcp add --transport sse llmtxt https://mcp.llmtxt.dev/sse

Text Corpus Analysis As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install text-corpus-analysis@danielrosehill

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

Only LLM Text has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Text Corpus Analysis publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: LLM Text · What it can do: Text Corpus Analysis · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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