Ext Ops Panel
Open dashboard
Comparison

Eco-Optimizer vs io.github.keshrath/agent-discover

Eco-Optimizer is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.keshrath/agent-discover is an MCP server published by keshrath. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). 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

Where each is published
MarketplaceEco-Optimizerio.github.keshrath/agent-discover
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 3.2.2
Downloads/month (npm): 2 387
Downloads/week (npm): 214
Forks (GitHub): 3
Stars (GitHub): 7
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.3.7
Forks (GitHub): 3
Stars (GitHub): 7
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

Eco-Optimizer vs io.github.keshrath/agent-discover
FactEco-Optimizerio.github.keshrath/agent-discover
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub7
Forks (GitHub) (differs)No figure on GitHub3
Last releaseNot publishedNot published
Where it runs (differs)Remote server (eco-optimizer-mcp.vercel.app/api/mcp)On your machine (agent-discover)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/keshrath/agent-discover
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 402 (32 h ago)no remote endpoint we check

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

Eco-Optimizer

In its own words, on Official MCP Registry:

Green computing task scheduler routing jobs to low-carbon zones.

io.github.keshrath/agent-discover

In its own words, on Official MCP Registry:

Find, install and enable MCP servers mid-session on any host, with consent and tool pinning

How to run each

Eco-Optimizer As a remote MCP server

Claude Code
claude mcp add --transport sse eco-optimizer https://eco-optimizer-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: payment-signature header

io.github.keshrath/agent-discover As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-discover -- npx -y agent-discover

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

Only Eco-Optimizer 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: Eco-Optimizer · What it can do: io.github.keshrath/agent-discover · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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