Ext Ops Panel
Open dashboard
Comparison

aicharged.io vs KEPTA — the memory for AI systems

aicharged.io is an MCP server published by aicharged.io. Marketplaces we read that list it: 1 (Official MCP Registry). KEPTA — the memory for AI systems is an MCP server published by DamianTodorovic. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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
Marketplaceaicharged.ioKEPTA — the memory for AI systems
Official MCP Registry Listed
Version: 1.1.0
No figure published
Not marked · First seen
Listed
Version: 3.4.0
Downloads/month (npm): 5 290
Downloads/week (npm): 210
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 3.4.0
Downloads/month (npm): 5 290
Downloads/week (npm): 210
Forks (GitHub): 0
Stars (GitHub): 2
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

aicharged.io vs KEPTA — the memory for AI systems
Factaicharged.ioKEPTA — the memory for AI systems
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-14
Where it runs (differs)Remote server (aicharged.io/api/v1/mcp)On your machine (kepta-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedBUSL-1.1
Repository (differs)Not statedgithub.com/damiantodorovic/kepta
Changes in the last 7 days00
First seen (differs)2026-10-222026-10-11
Endpoint at the last check (differs)Responded 9 h ago, requires a keyno 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

aicharged.io

In its own words, on Official MCP Registry:

214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.

KEPTA — the memory for AI systems

In its own words, on Official MCP Registry:

Local encrypted memory for AI: hybrid search, 8 MCP tools, one file you own. Free, no cloud.

How to run each

aicharged.io As a remote MCP server

Claude Code
claude mcp add --transport http aicharged https://aicharged.io/api/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

KEPTA — the memory for AI systems As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio kepta -- npx -y kepta-mcp

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

Only aicharged.io 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: aicharged.io · What it can do: KEPTA — the memory for AI systems · 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