Ext Ops Panel
Open dashboard
Comparison

mnemopay vs io.github.singularityjason/lightning-memory

mnemopay is a plugin bundle for AI coding tools published by mnemopay. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.singularityjason/lightning-memory is an MCP server published by singularityjason. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacemnemopayio.github.singularityjason/lightning-memory
Claude Code: claude-plugins-community Listed
Version: 1.2.0
Forks (GitHub): 4
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.1
Downloads/month (PyPI): 75
Downloads/week (PyPI): 17
Forks (GitHub): 5
Stars (GitHub): 9
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

mnemopay vs io.github.singularityjason/lightning-memory
Factmnemopayio.github.singularityjason/lightning-memory
Marketplaces that list it11
Stars (GitHub) (differs)8 (worse)9 (better)
Forks (GitHub) (differs)4 (worse)5 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@mnemopay/sdk)On your machine (lightning-memory)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)9Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/mnemopay/mnemopay-sdkgithub.com/singularityjason/lightning-memory
Changes in the last 7 days00
First seen2026-10-112026-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

mnemopay

In its own words, on Claude Code: claude-plugins-community:

Payment infrastructure for AI agents. Agent Credit Score (300-850), real payment rails (Stripe/Paystack/Lightning), autonomous shopping with escrow, hash-chained ledger, and behavioral finance. Charge for tool usage, track spending, shop autonomously, and build agent creditworthiness all from Claude Code.

io.github.singularityjason/lightning-memory

In its own words, on Official MCP Registry:

Decentralized agent memory for the Lightning economy. Nostr identity, L402 payments.

How to run each

mnemopay As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mnemopay@claude-community

io.github.singularityjason/lightning-memory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio lightning-memory -- uvx lightning-memory

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

The marketplaces of io.github.singularityjason/lightning-memory publish no settings it asks for, so we do not compare settings.

What it can do: mnemopay · What it can do: io.github.singularityjason/lightning-memory · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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