LLM Router vs JarvisClaw — AI Gateway & API Marketplace
LLM Router is a plugin bundle for AI coding tools published by ypollak2. Marketplaces we read that list it: 1 (Community GitHub marketplaces). JarvisClaw — AI Gateway & API Marketplace is an MCP server published by api-jarvisclaw. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-15. 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 |  JarvisClaw — AI Gateway & API Marketplace | |
|---|---|---|
| Community marketplace ypollak2/llm-router | Listed Version: 16.0.0 Forks (GitHub): 17 Stars (GitHub): 129 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 Downloads/month (npm): 138 Downloads/week (npm): 57 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
| Fact | LLM Router | JarvisClaw — AI Gateway & API Marketplace |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 129 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 17 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (llm-routing) | Remote server (api.jarvisclaw.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 16 | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ypollak2/llm-router | github.com/api-jarvisclaw/jarvisclaw-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 13 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 Router
Route text, image, video, and audio tasks to 20+ AI providers with smart routing, budget control, and multi-step orchestration
JarvisClaw — AI Gateway & API Marketplace
320 AI models + 2,720 pay-per-call APIs. x402 USDC on Base or Solana, no API key.
How to run each
LLM Router As a Claude Code plugin
/plugin marketplace add ypollak2/llm-router
/plugin install llm-router@ypollak2JarvisClaw — AI Gateway & API Marketplace As a remote MCP server
claude mcp add --transport http jarvisclaw https://api.jarvisclaw.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only JarvisClaw — AI Gateway & API Marketplace 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 Router · What it can do: JarvisClaw — AI Gateway & API Marketplace · 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.