io.github.STiFLeR7/memex vs NEAT
io.github.STiFLeR7/memex is an MCP server published by STiFLeR7. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). NEAT is an MCP server published by neat-technologies. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-23. 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 |  io.github.STiFLeR7/memex |  NEAT |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (npm): 602 Downloads/week (npm): 50 Forks (GitHub): 0 Stars (GitHub): 12 Not marked · First seen |
Listed Version: 0.10.9 Downloads/month (npm): 7 959 Downloads/week (npm): 1 390 Forks (GitHub): 1 Stars (GitHub): 22 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.3.2 Forks (GitHub): 0 Stars (GitHub): 0 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 | io.github.STiFLeR7/memex | NEAT |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 12 (worse) | 22 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | On your machine (stifler-memex-mcp) | On your machine (@neat.is/mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | 1, secrets among them: 0 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | 1 | 3 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/stifler7/memex | github.com/neat-technologies/neat |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-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.STiFLeR7/memex
Temporal engineering context for agents via MCP.
NEAT
A live graph of your running system, code fused with OTel runtime, that your agent queries over MCP.
How to run each
io.github.STiFLeR7/memex As a local MCP server: npm package
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "NEO4J_PASSWORD=<YOUR_NEO4J_PASSWORD>" --env "NEO4J_URI=<YOUR_NEO4J_URI>" --env "NEO4J_USER=<YOUR_NEO4J_USER>" --transport stdio memex -- npx -y stifler-memex-mcp serve --repo .Requires: GEMINI_API_KEY (secret), NEO4J_PASSWORD (secret), NEO4J_URI, NEO4J_USER
NEAT As a local MCP server: npm package
claude mcp add --transport stdio neat -- npx -y @neat.is/mcpCommands 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
Only io.github.STiFLeR7/memex asks for
GEMINI_API_KEY (secret)NEO4J_PASSWORD (secret)NEO4J_URINEO4J_USER
Only NEAT asks for
NEAT_CORE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.STiFLeR7/memex · What it can do: NEAT · 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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.