ai.llmintel/llmintel vs LLM Provider Intelligence
ai.llmintel/llmintel is an MCP server published by llmintel.ai. Marketplaces we read that list it: 1 (Official MCP Registry). LLM Provider Intelligence is an MCP server published by memoryapi.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
| Marketplace |   ai.llmintel/llmintel | |
|---|---|---|
| Official MCP Registry | Listed, marked deprecated Version: 0.1.1 Downloads/month (npm): 312 Downloads/week (npm): 90 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | ai.llmintel/llmintel | LLM Provider Intelligence |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (intel.memoryapi.org/mcp) |
| Transport (differs) | stdio, Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/hivemindunit/llmintel-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 47 h ago | Responded 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.llmintel/llmintel
Check whether an LLM model id is deprecated, retiring, or retired, and what to migrate to.
LLM Provider Intelligence
LLM provider intelligence: recommendations, pricing, and status
How to run each
ai.llmintel/llmintel As a local MCP server: npm package
claude mcp add --env "LLMINTEL_API_KEY=<YOUR_LLMINTEL_API_KEY>" --transport stdio llmintel -- npx -y @llmintel/mcpRequires: LLMINTEL_API_KEY (secret)
LLM Provider Intelligence As a remote MCP server
claude mcp add --transport http intel https://intel.memoryapi.org/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily 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
The marketplaces of LLM Provider Intelligence publish no settings it asks for, so we do not compare settings.
What it can do: ai.llmintel/llmintel · What it can do: LLM Provider Intelligence · Compare two other plugins
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.