Ext Ops Panel
Open dashboard
Comparison

llm-eval vs Amicus

llm-eval is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

llm-eval is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. Amicus is an MCP server published by BourbonDog. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacellm-evalAmicus
Community marketplace barnburner121/claude-plugin-marketplace Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.14.3
Downloads/month (npm): 2 921
Downloads/week (npm): 718
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-eval vs Amicus
Factllm-evalno longer listed · Amicus
Marketplaces that list it (differs)01
Stars (GitHub) (differs)32
Forks (GitHub)00
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (@barnburner121/plugin-hub-mcp)On your machine (amicus)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/barnburner121/claude-plugin-marketplacegithub.com/bourbondog/amicus
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of llm-eval

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • eval-genius

    Decide, design, gate, judge, and defend evaluations for LLM, agent, and retrieval systems. Not ordinary unit tests.

    by Alex Greenshpun · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • promptfoo-evaluation

    Configures and runs LLM evaluation using Promptfoo framework. Use when setting up prompt testing, creating evaluation configs (promptfooconfig.yaml), writing Python custom…

    by daymade · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ai-virtuoso

    2 AI engineering skills: LLM evals and LLM observability

    by krzysztofsurdy · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • EvalForge Lite

    Compare text LLMs across OpenRouter, Bedrock, Vertex AI and Foundry with automated grading.

    by thejaredchapman · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • DeepEval

    Skills for adding DeepEval evaluations, tracing, datasets, Confident AI reports, and iterative improvement loops to AI applications.

    by confident-ai · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Community GitHub marketplaces · Describes nearly the same job

  • skill-optimizer

    Benchmark, evaluate, and optimize skills to ensure reliable performance across all LLMs

    by Fast · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

llm-eval

In its own words, on Community GitHub marketplaces:

Generate LLM evaluation and benchmarking

Amicus

In its own words, on Official MCP Registry:

Multi-model LLM Council and parallel AI window for Claude Code. Fork any model, fold results back.

How to run each

llm-eval

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

Amicus As a local MCP server: npm package

Claude Code
claude mcp add --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --transport stdio amicus -- npx -y amicus mcp

Requires: OPENROUTER_API_KEY (secret)

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

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-eval publish no settings it asks for, so we do not compare settings.

What it can do: llm-eval · What it can do: Amicus · 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. 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