Ext Ops Panel
Open dashboard
Comparison

io.github.grossiweb/toolroute vs tierproxy

io.github.grossiweb/toolroute is an MCP server published by grossiweb. Marketplaces we read that list it: 1 (Official MCP Registry). tierproxy is an MCP server published by tierproxy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplaceio.github.grossiweb/toolroutetierproxy
Official MCP Registry Listed
Version: 0.2.2
Downloads/month (npm): 4 646
Downloads/week (npm): 1 657
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.4.0
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

io.github.grossiweb/toolroute vs tierproxy
Factio.github.grossiweb/toolroutetierproxy
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@toolroute/sdk)On your machine (tierproxy)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/grossiweb/toolroutegithub.com/tierproxy/python-sdk
Changes in the last 7 days00
First seen2026-10-112026-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

io.github.grossiweb/toolroute

In its own words, on Official MCP Registry:

Route AI agent tasks to the best MCP server and LLM, scored on 132+ real benchmark executions.

tierproxy

In its own words, on Official MCP Registry:

Multi-provider proxy infrastructure for AI/ML. Geo, sessions, cost-aware routing, usage tools.

How to run each

io.github.grossiweb/toolroute As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio toolroute -- npx -y @toolroute/sdk

tierproxy As a local MCP server: PyPI package

Claude Code
claude mcp add --env "TIERPROXY_API_KEY=<YOUR_TIERPROXY_API_KEY>" --transport stdio python-sdk -- uvx --spec "tierproxy[mcp]" tierproxy tierproxy-mcp

Requires: TIERPROXY_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 io.github.grossiweb/toolroute publish no settings it asks for, so we do not compare settings.

What it can do: io.github.grossiweb/toolroute · What it can do: tierproxy · 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.

Where the data comes from: how the catalog is built