com.memfleet/memfleet vs EMET
com.memfleet/memfleet is an MCP server published by memfleet.com. Marketplaces we read that list it: 1 (Official MCP Registry). EMET is an MCP server published by dreamforgestudiollc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  com.memfleet/memfleet |   EMET |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.2 Downloads/month (npm): 270 Downloads/week (npm): 39 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 | com.memfleet/memfleet | EMET |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Remote server (memfleet.com/mcp) | On your machine (@dreamforgestudiollc/emet) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/oren198/memfleet | github.com/dreamforgestudiollc/emet |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-26 | 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
com.memfleet/memfleet
Shared, governed memory for fleets of AI agents: judged contributions, provenance, operator control
EMET
0.3.2. Free MIT; no account, key, or payment. Verifies record, not computation. Stable error codes.
How to run each
com.memfleet/memfleet As a remote MCP server
claude mcp add --transport http memfleet https://memfleet.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
EMET As a local MCP server: npm package
claude mcp add --env "MONGODB_URI=<YOUR_MONGODB_URI>" --transport stdio emet -- npx -y @dreamforgestudiollc/emetRequires: MONGODB_URI (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.memfleet/memfleet 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 com.memfleet/memfleet publish no settings it asks for, so we do not compare settings.
What it can do: com.memfleet/memfleet · What it can do: EMET · 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.