Ext Ops Panel
Open dashboard
Comparison

iris-eval vs tokencast

iris-eval is a plugin bundle for AI coding tools published by Iris. Marketplaces we read that list it: 1 (Community GitHub marketplaces). tokencast is an MCP server published by krulewis. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplaceiris-evaltokencast
Community marketplace iris-eval/mcp-server Listed
Version: 0.20.0
Forks (GitHub): 4
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (PyPI): 91
Downloads/week (PyPI): 65
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

iris-eval vs tokencast
Factiris-evaltokencast
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 (better)2 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@iris-eval/mcp-server)On your machine (tokencast)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published4
Parts of the bundle (differs)25
Licence (differs)Not statedMIT
Repository (differs)github.com/iris-eval/mcp-servergithub.com/krulewis/tokencast
Changes in the last 7 days22
First seen (differs)2026-10-132026-10-11

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

iris-eval

In its own words, on Community GitHub marketplaces:

Stop shipping agents on vibes — agent eval for any MCP workflow. Score output quality, catch PII and prompt injection, verify citations, and enforce cost budgets. 12 MCP tools + the iris-eval skill.

tokencast

In its own words, on Official MCP Registry:

Pre-execution cost estimation for LLM agent workflows with calibration learning

How to run each

iris-eval As a Claude Code plugin

Claude Code
/plugin marketplace add iris-eval/mcp-server
/plugin install iris-eval@iris-eval

tokencast As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio tokencast -- uvx tokencast

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

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

What it can do: iris-eval · What it can do: tokencast · 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