Ext Ops Panel
Open dashboard
Comparison

io.github.Agentled/mcp-server vs CacheBash

io.github.Agentled/mcp-server is an MCP server published by Agentled. Marketplaces we read that list it: 1 (Official MCP Registry). CacheBash is an MCP server published by feelgreatfoodie. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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.Agentled/mcp-serverCacheBash
Official MCP Registry Listed
Version: 0.20.1
Downloads/month (npm): 858
Downloads/week (npm): 359
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 2.0.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.Agentled/mcp-server vs CacheBash
Factio.github.Agentled/mcp-serverCacheBash
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-15Not published
Where it runs (differs)On your machine (@agentled/mcp-server)Remote server (cachebash-mcp-922749444863.us-central1.run.app/v1/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/agentled/mcp-servergithub.com/rezzedai/cachebash
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 40 h ago, requires a key

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.Agentled/mcp-server

In its own words, on Official MCP Registry:

Intelligent AI workflow orchestration with long-term memory, 100+ integrations, and unified credits.

CacheBash

In its own words, on Official MCP Registry:

Let your AI sessions talk to each other — messaging, tasks, sessions, and alerts

How to run each

io.github.Agentled/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTLED_API_KEY=<YOUR_AGENTLED_API_KEY>" --transport stdio io-github-agentled-mcp-server -- npx -y @agentled/mcp-server

Requires: AGENTLED_API_KEY (secret)

CacheBash As a remote MCP server

Claude Code
claude mcp add --transport http cachebash https://cachebash-mcp-922749444863.us-central1.run.app/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only CacheBash 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 CacheBash publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Agentled/mcp-server · What it can do: CacheBash · 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