io.github.apexapi/apexapi-mcp vs OpenRouter
io.github.apexapi/apexapi-mcp is an MCP server published by apexapi. Marketplaces we read that list it: 1 (Official MCP Registry). OpenRouter is an MCP server published by tsilva. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  io.github.apexapi/apexapi-mcp |  OpenRouter |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 651 Downloads/week (npm): 40 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.8 Downloads/month (PyPI): 189 Downloads/week (PyPI): 98 Forks (GitHub): 0 Stars (GitHub): 1 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 | io.github.apexapi/apexapi-mcp | OpenRouter |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (apexapi-mcp) | On your machine (mcp-openrouter) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 6, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/apexapi/apexapi-mcp | github.com/tsilva/mcp-openrouter |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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.apexapi/apexapi-mcp
Call 120+ AI models and live web context (scrape/crawl/extract) from any MCP client with one key
OpenRouter
MCP server providing access to 300+ AI models via OpenRouter
How to run each
io.github.apexapi/apexapi-mcp As a local MCP server: npm package
claude mcp add --env "APEXAPI_API_KEY=<YOUR_APEXAPI_API_KEY>" --transport stdio apexapi-mcp -- npx -y apexapi-mcpRequires: APEXAPI_API_KEY (secret)
OpenRouter As a local MCP server: PyPI package
claude mcp add --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --transport stdio mcp-openrouter -- uvx mcp-openrouterRequires: 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
Only io.github.apexapi/apexapi-mcp asks for
APEXAPI_API_KEY (secret)
Only OpenRouter asks for
DEFAULT_CODE_MODELDEFAULT_EMBEDDING_MODELDEFAULT_IMAGE_MODELDEFAULT_TEXT_MODELDEFAULT_VISION_MODELOPENROUTER_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.apexapi/apexapi-mcp · What it can do: OpenRouter · 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.