Knot vs io.github.STiFLeR7/memex
Knot is an MCP server published by connectknot.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.STiFLeR7/memex is an MCP server published by STiFLeR7. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, PyPI (MCP servers)). As of our marketplace pass on 2026-11-07. 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 |   Knot |  io.github.STiFLeR7/memex |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.3 Downloads/month (npm): 892 Downloads/week (npm): 144 Forks (GitHub): 0 Stars (GitHub): 12 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.3.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.0.3 Downloads/month (PyPI): 255 Downloads/week (PyPI): 151 Forks (GitHub): 0 Stars (GitHub): 12 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
| Fact | Knot | io.github.STiFLeR7/memex |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 12 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-30 (better) | 2026-10-27 (worse) |
| Where it runs (differs) | Remote server (api.connectknot.com/mcp) | On your machine (stifler-memex-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/connectknot/knot-mcp | github.com/stifler7/memex |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-27 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 20 h ago | no 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
Knot
Shared brain, one current version of memory for any MCP client: ChatGPT, Claude, Gemini, Cursor
io.github.STiFLeR7/memex
Temporal engineering context for agents via MCP.
How to run each
Knot As a remote MCP server
claude mcp add --transport http knot https://api.connectknot.com/mcpio.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
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Knot 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 Knot publish no settings it asks for, so we do not compare settings.
What it can do: Knot · What it can do: io.github.STiFLeR7/memex · 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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.