LoreConvo vs uk.co.batterystoragecost/site
LoreConvo is an MCP server published by labyrinth-analytics. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). uk.co.batterystoragecost/site is an MCP server published by batterystoragecost.co.uk. 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
| Marketplace |  LoreConvo |  uk.co.batterystoragecost/site |
|---|---|---|
| Official MCP Registry | Listed Version: 0.10.20 Downloads/month (PyPI): 902 Downloads/week (PyPI): 380 Forks (GitHub): 1 Stars (GitHub): 12 Not marked · First seen |
Listed Version: 1.0.1 No figure published Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.9.0 Forks (GitHub): 1 Stars (GitHub): 12 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
| Fact | LoreConvo | uk.co.batterystoragecost/site |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 12 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | 2026-10-27 | Not published |
| Where it runs (differs) | On your machine (loreconvo) | Remote server (batterystoragecost.co.uk/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence (differs) | BSL-1.1 | Not stated |
| Repository (differs) | github.com/labyrinth-analytics/loreconvo | Not stated |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 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
LoreConvo
Local-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.
uk.co.batterystoragecost/site
Battery Storage Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
How to run each
LoreConvo As a local MCP server: PyPI package
claude mcp add --env "LORECONVO_PRO=<YOUR_LORECONVO_PRO>" --transport stdio loreconvo -- uvx loreconvoRequires: LORECONVO_PRO (secret)
uk.co.batterystoragecost/site As a remote MCP server
claude mcp add --transport http site https://batterystoragecost.co.uk/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only uk.co.batterystoragecost/site 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 uk.co.batterystoragecost/site publish no settings it asks for, so we do not compare settings.
What it can do: LoreConvo · What it can do: uk.co.batterystoragecost/site · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.