Ext Ops Panel
Open dashboard
Comparison

io.github.CodesWhat/portkey-admin-mcp vs Execute api-quota-balancer-mcp

io.github.CodesWhat/portkey-admin-mcp is an MCP server published by CodesWhat. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Execute api-quota-balancer-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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.CodesWhat/portkey-admin-mcpExecute api-quota-balancer-mcp
Official MCP Registry Listed
Version: 0.15.1
Downloads/month (npm): 1 620
Downloads/week (npm): 304
Forks (GitHub): 1
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 2.0.0
No figure published
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.15.1
Downloads/month (npm): 1 620
Downloads/week (npm): 304
Forks (GitHub): 1
Stars (GitHub): 6
Not marked · First seen
Not listed

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.CodesWhat/portkey-admin-mcp vs Execute api-quota-balancer-mcp
Factio.github.CodesWhat/portkey-admin-mcpExecute api-quota-balancer-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)6No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last release (differs)2026-10-27Not published
Where it runs (differs)On your machine (portkey-admin-mcp)Remote server (api.m2mcent.com/api-quota-balancer-mcp/sse)
Transport (differs)stdioSSE
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/codeswhat/portkey-admin-mcpNot stated
Changes in the last 7 days (differs)60
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 402 (3 days 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

io.github.CodesWhat/portkey-admin-mcp

In its own words, on Official MCP Registry:

Portkey Admin API control-plane MCP server with Prisma AIRS interoperability guidance.

Execute api-quota-balancer-mcp

In its own words, on Official MCP Registry:

Premium agentic endpoint for api-quota-balancer-mcp.

How to run each

io.github.CodesWhat/portkey-admin-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "PORTKEY_API_KEY=<YOUR_PORTKEY_API_KEY>" --transport stdio portkey-admin-mcp -- npx -y portkey-admin-mcp

Requires: PORTKEY_API_KEY (secret)

Execute api-quota-balancer-mcp As a remote MCP server

Claude Code
claude mcp add --transport sse api-quota-balancer-mcp https://api.m2mcent.com/api-quota-balancer-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: Payment-Signature header

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

Only Execute api-quota-balancer-mcp 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

The marketplaces of Execute api-quota-balancer-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.CodesWhat/portkey-admin-mcp · What it can do: Execute api-quota-balancer-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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