Ext Ops Panel
Open dashboard
Comparison

LLM Text vs io.github.humantextpro/mcp-server

LLM Text is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.humantextpro/mcp-server is an MCP server published by humantextpro. Marketplaces we read that list it: 1 (Official MCP Registry). 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 Textio.github.humantextpro/mcp-server
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
Downloads/month (npm): 172
Downloads/week (npm): 35
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

LLM Text vs io.github.humantextpro/mcp-server
FactLLM Textio.github.humantextpro/mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.llmtxt.dev/sse)On your machine (@humantext/mcp-server)
Transport (differs)SSEstdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/humantextpro/mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
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.

io.github.humantextpro/mcp-server

In its own words, on Official MCP Registry:

AI text detection and humanization for Claude Code, Cursor, and Windsurf.

How to run each

LLM Text As a remote MCP server

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

io.github.humantextpro/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "HUMANTEXT_API_KEY=<YOUR_HUMANTEXT_API_KEY>" --transport stdio io-github-humantextpro-mcp-server -- npx -y @humantext/mcp-server

Requires: HUMANTEXT_API_KEY (secret)

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 io.github.humantextpro/mcp-server publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of LLM Text publish no settings it asks for, so we do not compare settings.

What it can do: LLM Text · What it can do: io.github.humantextpro/mcp-server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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