Ext Ops Panel
Open dashboard
Comparison

io.github.CloudCorpRecords/scentindex vs Search Memory

io.github.CloudCorpRecords/scentindex is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). Search Memory is an MCP server published by kefyusuf. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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.CloudCorpRecords/scentindexSearch Memory
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.2.0
Downloads/month (npm): 1 978
Downloads/week (npm): 374
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.2.0
Downloads/month (npm): 1 978
Downloads/week (npm): 374
Forks (GitHub): 0
Stars (GitHub): 1
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.CloudCorpRecords/scentindex vs Search Memory
Factio.github.CloudCorpRecords/scentindexSearch Memory
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-28
Where it runs (differs)On your machine (@reneturcios/scentindex)On your machine (search-memory-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 3
Licence (differs)Not statedISC
Repository (differs)github.com/cloudcorprecords/scentindexgithub.com/kefyusuf/search-memory-mcp
Changes in the last 7 days00
First seen (differs)2026-11-032026-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

io.github.CloudCorpRecords/scentindex

In its own words, on Official MCP Registry:

Search a fragrance index: perfumes, notes, houses and guides; similar scents and alternatives.

Search Memory

In its own words, on Official MCP Registry:

Free web search and long-term memory for AI assistants. No API keys; data stays local.

How to run each

io.github.CloudCorpRecords/scentindex As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio scentindex -- npx -y @reneturcios/scentindex mcp

Search Memory As a local MCP server: npm package

Claude Code
claude mcp add --env "BRAVE_SEARCH_API_KEY=<YOUR_BRAVE_SEARCH_API_KEY>" --env "EXA_API_KEY=<YOUR_EXA_API_KEY>" --env "TAVILY_API_KEY=<YOUR_TAVILY_API_KEY>" --transport stdio search-memory-mcp -- npx -y search-memory-mcp

Requires: BRAVE_SEARCH_API_KEY (secret), EXA_API_KEY (secret), TAVILY_API_KEY (secret)

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

What it can do: io.github.CloudCorpRecords/scentindex · What it can do: Search Memory · 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