Ext Ops Panel
Open dashboard
Comparison

llm-checker vs Local AI Prices

llm-checker is an MCP server published by signerless. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Local AI Prices is an MCP server published by localaiprices.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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-checkerLocal AI Prices
npm registry (MCP servers) Listed
Version: 3.8.2
Downloads/month (npm): 2 715
Downloads/week (npm): 1 038
Forks (GitHub): 205
Stars (GitHub): 3 054
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

llm-checker vs Local AI Prices
Factllm-checkerLocal AI Prices
Marketplaces that list it11
Stars (GitHub) (differs)3 054No figure on GitHub
Forks (GitHub) (differs)205No figure on GitHub
Last release (differs)2026-10-14Not published
Where it runs (differs)On your machine (llm-checker)Remote server (localaiprices.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)SEE LICENSE IN LICENSENot stated
Repository (differs)github.com/signerless/llm-checkerNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-05
Endpoint at the last check (differs)no remote endpoint we checkResponded 22 h 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

llm-checker

In its own words, on npm registry (MCP servers):

Intelligent CLI tool with AI-powered model selection that analyzes your hardware and recommends optimal LLM models for your system

Local AI Prices

In its own words, on Official MCP Registry:

Daily prices, stock and measured LLM speeds for local AI computers and graphics cards.

How to run each

llm-checker

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Local AI Prices As a remote MCP server

Claude Code
claude mcp add --transport http localaiprices https://localaiprices.com/mcp

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

Only Local AI Prices 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: llm-checker · What it can do: Local AI Prices · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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