Stellar Memory vs DualSPHysics MCP
Stellar Memory is an MCP server published by sangjun0000. Marketplaces we read that list it: 1 (Official MCP Registry). DualSPHysics MCP is an MCP server published by vegetableno1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  DualSPHysics MCP | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (npm): 311 Downloads/week (npm): 94 Not marked · First seen |
Listed Version: 0.2.0 Downloads/month (PyPI): 437 Downloads/week (PyPI): 32 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
| Fact | Stellar Memory | DualSPHysics MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (stellar-memory) | On your machine (dualsphysics-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 0 | 6, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/vegetableno1/dualsphysics-mcp |
| Changes in the last 7 days | 0 | 0 |
| 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
Stellar Memory
Persistent AI memory using orbital mechanics. 100% local, zero API keys, MCP-native.
DualSPHysics MCP
Agent toolchain for the DualSPHysics SPH solver: case creation, runs, post-processing, validation.
How to run each
Stellar Memory As a local MCP server: npm package
claude mcp add --transport stdio stellar-memory -- npx -y stellar-memoryDualSPHysics MCP As a local MCP server: PyPI package
claude mcp add --transport stdio dualsphysics -- uvx dualsphysics-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 Stellar Memory asks for
STELLAR_API_PORTSTELLAR_DB_PATHSTELLAR_PROJECTSTELLAR_SUN_TOKEN_BUDGET
Only DualSPHysics MCP asks for
DSPH_GENCASEDSPH_JOBS_DIRDSPH_MEASURETOOLDSPH_OMP_THREADSDSPH_PARTVTKDSPH_SOLVER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Stellar Memory · What it can do: DualSPHysics MCP · Compare two other plugins
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.